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
kay, last issue of the day before actually doing something 😄
I would like to indulge my OCD and refactor the tests directory to take a {name}.py -> test_{name}.py structure. By that paradigm, we're currently missing test_core.py and test_buffered.py... it's all getting tested, since our coverage is ≈97%, but I'm finding it less than obvious how / where to dive in and start making changes.
I am not offended by this, go for it as far as I'm concerned.
I have two bonus thoughts about this (these are on principle, requiring no actual changes to your proposals... yet)
I agree in general about {name}.py -> test_{name}.py, with the following modifications:
Due to the py.test inability to handle multiple test files with the same name, I usually do: {submodule}/{name}.py => test_{submodule}_{name}.py
although that doesn't matter to us yet. (But would on your transforms proposal)
To me Integration/system tests or the like also don't necessarily follow this convention.
kay, last issue of the day before actually doing something 😄
I would like to indulge my OCD and refactor the tests directory to take a
{name}.py -> test_{name}.py
structure. By that paradigm, we're currently missingtest_core.py
andtest_buffered.py
... it's all getting tested, since our coverage is ≈97%, but I'm finding it less than obvious how / where to dive in and start making changes.what say you @cjacoby @bmcfee?
The text was updated successfully, but these errors were encountered: