-
Notifications
You must be signed in to change notification settings - Fork 22
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
Build Unit test boilerplate #1052
Conversation
Had to rename flowcb/accept/delete_test.py becase there's on here too.
authenticate, destfn, download, filter, gather
…nstead There's also some test renames as well for cases where there's duplicate module names in different folders. They're now "<moduleName>__<ParentFolder>_test.py" Also removed un-neccessary imports from the boilerplate test files
Includes: accept, housekeeping, post, scheduled, send Rename conflicting modules from other flowcb folders
Test Results220 tests 212 ✅ 17s ⏱️ Results for commit b0728af. ♻️ This comment has been updated with latest results. |
You didn't ask for any reviewers... (top-right?) |
Added a ton of files, most of which are empty, containing no tests.
They're just there to setup the ground-work for future tests.
I also centralized the "debug" stuff into the
conftest.py
file in the root of the tests directory. Now when looking to debug anything during test writing, you can just calldebug.pretty(YourThingToDebug)
, and it should work.It's also possible to centralize some fixtures there if needed. Things like building a base config, or messages could be put there, and used by all tests.
You can also create a
conftest.py
file in any given directory, and have those contents be available in that context, either building on those defined above it, or over-riding them.Some of that is outlined here