-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor integration test fixtures and implement direct_message integration test #238
Conversation
On my system |
Oops I pushed the direct message commits again before rebasing. Fixing that. |
093677c
to
55484ea
Compare
The tests specific to this PR are fixed but now another failed. Flaky test? |
Don't understand... This test passes reliably locally 😭 |
1d94b19
to
474f436
Compare
0f20271
to
97da7a9
Compare
Reviving this PR. After further testing it turns out the problem is launching the bot through fixtures. Previously To workaround I added |
Code Climate has analyzed commit 855fb38 and detected 0 issues on this pull request. View more on Code Climate. |
…ration test (attzonko#238) * Fix docs monospace styling * Test replies via direct messages
Trying to address @jneeven 's request in #233 about integration tests.
Before that I need more control over when fixtures are initialized so removing
autouse=True
, making them scoped tomodule
instead ofsession
and also making both starting the bot and the driver as explicit fixture dependencies.