not collect deselected tests

[pytestbot]

Originally reported by: Anonymous

---

Some tests can be generating multiple tests through @pytest.mark.parametrize() or metafunc.parametrize, however if those tests are marked and specified not to run (through -m "not marker" command line argument) they are still collected first and then are deselected.

In my specific case, one of @pytest.mark.parametrize() is generating around 500 tests - only to be deselected afterwards. This makes a long test even longer.

Suggestion: to add an option not to generate (or not to collect) tests that are not required.

Thanks!

---

• Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/239

[pytestbot]

Original comment by Alex Okrushko (BitBucket: alex_okrushko, GitHub: alex_okrushko):

---

forgot to log in first

[pfctdayelise]

One thing I am worried about is that you maybe can't know until the test has been collected. This would be unsafe for sure with -k, maybe with -m it is safer. But for example a fixture can dynamically add a marker. So you'd want to have that happen before selecting tests.

[RonnyPfannschmidt]

Sounds like we still can do a best effort

[pfctdayelise]

True, we could do it twice.

[RonnyPfannschmidt]

as far as i can tell, we can make collectors bail out early, we'd still have to report the bailout in some way and figure how to do report collector deselection

its def not a easy or short term task

[RonnyPfannschmidt]

Closing, the issue should be tackled with better collection