Rune Tynan

Any update on this? Travis started allowing automatic migration a while ago

Assigning the variable is an option, I'm working on improving that default assert message. Most likely I'll be making the verify stringify/repr output include details about how the assertion failed,...

Note: The new style is about the same number of characters as the old `verify_message` for the same result, but both are definitely a bit longer than just `assert CONTENT...

Personally, I prefer to use a more minimal form of sphynx, relying on type hints instead of `:type:`. This works well with readthedocs, as the signature is already included so...

Some thoughts on 'more assertion functions': Given the gradual increase in flags, I think it may be worth it to go the way of libraries like `junit` or such, where...

I opened a PR for my proposed change (#49). I believe the predicate/builder style is more in keeping with the pytest philosophy of explicit asserts, and that we will need...

Implemented starting support for reactions, please try updating to the most recent version. If the issue still isn't fixed, I need to add the more specific reaction handlers.

Failure when content is None is #26, introduced due to changes on how the backend handless messages. That should be fixed soon, apologies on the regression

Currently, there's no separate support server or such, I may make one soon. From the code you posted, the line `async def test_chat_muse(bot):` won't invoke the fixture `chat_bot`, the parameter...

It has been a long time, but I personally figured out the issue recently while writing the tests for this library. The `bot` fixture should use the `event_loop` fixture and...