-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Configure test discovery as per pytest good practices #83
Labels
enhancement
New feature or request
Comments
This was referenced Jan 14, 2022
@arshadkazmi42 Any experience with pyproject.toml? |
No. Haven't worked with it before |
2 tasks
arshadkazmi42
added a commit
that referenced
this issue
Jan 15, 2022
refactored using __init__ and class import for #83
This was referenced Jun 19, 2022
Merged
kgashok
added a commit
to kgashok/first-issues
that referenced
this issue
Jun 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test discovery is best handled by adopting good practices.
I suggest we move in a phased manner. Begin by adopting good practices for tests outside application code, which is the way it is currently configured.
From ~2013 (from
unittest
era), read Kenneth Reitz suggested test suite structure hereconsidering the use of importlib
restructuring the repo with /src layout
conftest.py seems to be versatile
write some more tests
The text was updated successfully, but these errors were encountered: