Need a programmatic way to register markers

[charris]

The latest (4.5.0) pytest release raises a warning when non-registered markers are discovered in the discovery phase. That can be fixed by registering the markers in the pytest.ini file as long as that file is present and findable, however, that is not the case when testing NumPy installed from wheels or using setup.py, as the tests are run from the imported NumPy module. What would be helpful is if there were a way to register the marks from the pytest command line or possibly during the discovery phase. There may already be such a method, but I am unable to find it in the documentation.

• a detailed description of the bug or suggestion
• output of pip list from the virtual environment you are using
• pytest and operating system versions
• minimal example if possible

[RonnyPfannschmidt]

the common workaround

pytest/src/_pytest/skipping.py

Lines 47 to 70 in 6a43c8c

	config.addinivalue_line(
	"markers",
	"skip(reason=None): skip the given test function with an optional reason. "
	'Example: skip(reason="no way of currently testing this") skips the '
	"test.",
	)
	config.addinivalue_line(
	"markers",
	"skipif(condition): skip the given test function if eval(condition) "
	"results in a True value. Evaluation happens within the "
	"module global context. Example: skipif('sys.platform == \"win32\"') "
	"skips the test if we are on the win32 platform. see "
	"https://docs.pytest.org/en/latest/skipping.html",
	)
	config.addinivalue_line(
	"markers",
	"xfail(condition, reason=None, run=True, raises=None, strict=False): "
	"mark the test function as an expected failure if eval(condition) "
	"has a True value. Optionally specify a reason for better reporting "
	"and run=False if you don't even want to execute the test function. "
	"If only specific exception(s) are expected, you can list them in "
	"raises, and if the test fails in other ways, it will be reported as "
	"a true failure. See https://docs.pytest.org/en/latest/skipping.html",
	)

[charris]

Yes, but where should it be done?

[RonnyPfannschmidt]

your personal pytest_configure hook

[charris]

Thanks, that seems to work. Not sure why I could not find that bit of documentation, I did search.

[RonnyPfannschmidt]

tbh, its hard to search for it - https://docs.pytest.org/en/latest/example/markers.html#custom-marker-and-command-line-option-to-control-test-runs

[nicoddemus]

tbh, its hard to search for it

Agreed, trying to improve the docs in #5265.

[rgommers]

This issue is popping up in many places, I've personally encountered it in NumPy, SciPy and PyWavelets. Many projects use at least a slow mark. Can that be added to the builtin marks somehow if you really want to keep this warning and turn it into an error?

Also, conftest.py isn't a great name. import scipy.conftest really should not succeed, it looks like a public API.

@charris could you reopen this?

[nicoddemus]

Hi @rgommers,

This issue is popping up in many places, I've personally encountered it in NumPy, SciPy and PyWavelets.

What do you mean? Are you encountering this as a user or as a developer of those libraries?

[rgommers]

As a developer of those libraries mainly. But any user will see these if they run tests for NumPy, SciPy, PyWavelets or any other similar project if they install the latest pytest.