You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We always create a single test_* file in tests directory for each test trace ... call. So for a directory passed as a trace, it will create a tests/example_<TS>/test_example.py - a directory containing a single test.
Why not:
put single test_*.py files always in tests/ directory?
Or, we replace tests/example_<TS>/test_example.py with tests/example/test_example_<TS>.py. But then we should do the same for individual traces?
I [Rano] like (1) if we don't care about tests/test_*py. I like (2) because it organizes the tests directory.
The text was updated successfully, but these errors were encountered:
From #199 (comment) :
We always create a single
test_*
file in tests directory for eachtest trace
... call. So for a directory passed as a trace, it will create atests/example_<TS>/test_example.py
- a directory containing a single test.Why not:
test_*.py
files always in tests/ directory?tests/example_<TS>/test_example.py
withtests/example/test_example_<TS>.py
. But then we should do the same for individual traces?I [Rano] like (1) if we don't care about
tests/test_*py
. I like (2) because it organizes the tests directory.The text was updated successfully, but these errors were encountered: