Replies: 1 comment
-
|
ping @pytest-dev team on this question |
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
Uh oh!
There was an error while loading. Please reload this page.
-
We have a package (call it
cheese) that contains (in addition to the primary code) various test-helper functions & utility decorators that, among other things, apply custom markers to decorated tests. Various other packages that depend oncheesemake use of these helpers in their own tests, but because the markers are (currently) only defined in thetox.inifile incheese's repository, warnings about unknown markers are emitted when testing these other packages. The best way to solve this appears to be to declare the markers in apytest_configurehook, but that leads to the following questions:Is the only way to make the
pytest_configurehook take effect for other packages to turncheeseinto a pytest plugin?Where should we put the
pytest_configurehook so that it takes effect forcheese's own tests? Note thatcheese'sconftest.pyfile contains some autouse fixtures which we do not want used by other packages, so I expect that putting the hook in that file and pointing the pytest plugin to it would cause problems.Beta Was this translation helpful? Give feedback.
All reactions