Replies: 1 comment
-
FYI - In the meantime, I'm going to use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My repository looks something like this:
The structure inside
tests/
mirrors the structure of the repo, making it easy to keep tests organized and find the tests for a particular bit of code. For example, if I have a moduleutils/parsing.py
, then the tests for that will be intests/utils/test__parsing.py
.However, I have a lot of fixtures and homebrew test tools that are currently all shoved into conftest.py, which is now way too long and crowded.
I don't want to create a
tests/utils/
ortests/lib/
folder insidetests/
for that code because that violates the namespace - iftests/utils/
contains utilities for testing, there where do I put the tests for myutils/
code? The tests that currently live intests/utils/
?There's only one name in the
tests/
namespace that is explicitly for the purpose of storing code to aid in testing, and that'sconftest.py
. So why not allow me to expand that into a directory?Beta Was this translation helpful? Give feedback.
All reactions