Naming of dataclasses: integration tests warn of pytestcollection warning #1233
niksheridan
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is it useful to name the dataclasses with a TestXXXXX prefix, as when making assertions with pytest and importing this dataclass this appears to create confusion in collection? (for example)
I always try to reuse unless forced not to. Reduction of cosmetic or informational errors in test output helps increase focus on the real source of unexpected behaviour.
I suppose this is similar to prefixing a function with test_XXX not using it for integration or unit testing.
Please do not take this as a criticism, I very much like the code in this repo 🤩
Has anyone worked around this?
Beta Was this translation helpful? Give feedback.
All reactions