You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feature is request to keep nose users, not to push them away by a single incompatible feature.
I got used to nosetests -vv ./tests/foo/test_boo.py
when switched to nose2
this is not supported any more, nose2 -v ./tests/foo/test_boo.py, after a file was edited with vim ./tests/foo/test_boo.py, it is only natural going to test with file name, not the dot format.
After all the frustration, I found: pytest -v ./tests/foo/test_boo.py is supported
but not all the tests are compatible with both nose2 and pytest.
The implementation should be easy, just be sure why it is not implemented, and no one seems to be complaint about it.
Thanks
The text was updated successfully, but these errors were encountered:
I would like to do this, but I would not go in assuming that it will be easy.
In order to maintain compatibility with existing usage, I think we'd want to try to process the first argument as a module name, and then as a file if that fails.
Introducing a bunch of flags and modes to handle this would be "more explicit", and easier to maintain, but also sounds like a nightmare to use.
The feature is request to keep nose users, not to push them away by a single incompatible feature.
I got used to
nosetests -vv ./tests/foo/test_boo.py
when switched to
nose2
this is not supported any more,
nose2 -v ./tests/foo/test_boo.py
, after a file was edited withvim ./tests/foo/test_boo.py
, it is only natural going to test with file name, not the dot format.After all the frustration, I found:
pytest -v ./tests/foo/test_boo.py
is supportedbut not all the tests are compatible with both
nose2
andpytest
.The implementation should be easy, just be sure why it is not implemented, and no one seems to be complaint about it.
Thanks
The text was updated successfully, but these errors were encountered: