Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support nose2 -v ./tests/foo/test_boo.py #399

Open
EverydayQA opened this issue May 30, 2018 · 2 comments
Open

support nose2 -v ./tests/foo/test_boo.py #399

EverydayQA opened this issue May 30, 2018 · 2 comments
Labels

Comments

@EverydayQA
Copy link

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

@katrinabrock
Copy link
Collaborator

Seems like a good feature. Would accept a PR if anyone wants to work on it.

@sirosen
Copy link
Collaborator

sirosen commented Dec 9, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants