pytest stops collecting tests when pysaunter release is newer than 0.50 about py.saunter

[carolmirakove]

@alexi0us check the pytest.ini. If your test functions and classes don't start with Check or test they won't be picked up.

[alexi0us]

@carolmirakove Thanks for your reply. All my tests start with test :-).
I am able to run the tests without any problems with the package list listed above (pysaunter 0.5). As soon as I update pysaunter, collection returns 0 tests. Its very weird problem.
It took me a day of debugging to understand that this issue is related to pysaunter - in the beginning I thought I was doing something wrong with pytest. To me it looks like that there is some kind of incompatibility between pytest and pysaunter versions but I can't really say what that is.

Cheers
Alexis

[carolmirakove]

Ah well, sorry it wasn't that easy! I've seen that problem in the past so I thought it was worth a shot :)
FWIW I am running Py.Saunter 0.56 and pytest-2.3.4 with no problems.

[alexi0us]

No problem. Its always good to ask the obvious questions :-)
I have updated pytest to 2.3.4 and py,saunter to 0.56 but still the same result. Not sure if its related but whats your py-marks version?

[carolmirakove]

I've got pytest-marks 0.4

[alexi0us]

From the release notes :
because the unittest stuff is gone, the collection algorithm is slightly different, which means the rules in pytest.ini are now being followed. The original rule that was unenforced was that your test methods must start with Check. CheckFoo, CheckBar, CheckFlyingMonkey etc. If you are using Test, or Scalpel or whatever, you can tweak the python_classes line to have the prefix you are using, or if you are using multiple prefixes it is a space delimited list.

Sorry for that. I was blind!