Skip to content

Selecting a test by its node id not documented #499

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

Closed
pytestbot opened this issue Apr 4, 2014 · 3 comments
Closed

Selecting a test by its node id not documented #499

pytestbot opened this issue Apr 4, 2014 · 3 comments
Labels
type: bug problem that needs to be addressed type: docs documentation improvement, missing or needing clarification

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Jurko Gospodnetić (BitBucket: jurko, GitHub: jurko)


Selecting a test by its node id is not documented anywhere.

This issue has been extracted out of issue #387 because the original issue got marked as resolved. The following is a copy/paste of a related message in the original issue:

In this specific case one can already select just a single test by
using the node ID. Assuming these live in the test_foo file:

py.test -v test_foo::TestAlice::test_foo

or

py.test -v test_foo::TestAlice

work fine.

And to find out the node IDs one can use --collectonly.

Hope this helps.

Best regards,
Jurko Gospodnetić


@pytestbot
Copy link
Contributor Author

Original comment by Floris Bruynooghe (BitBucket: flub, GitHub: flub):


Merged in rouge8/pytest/issue499 (pull request #157)

fix issue499: document selecting tests by node ID

1 similar comment
@pytestbot
Copy link
Contributor Author

Original comment by Floris Bruynooghe (BitBucket: flub, GitHub: flub):


Merged in rouge8/pytest/issue499 (pull request #157)

fix issue499: document selecting tests by node ID

@pytestbot
Copy link
Contributor Author

Original comment by Floris Bruynooghe (BitBucket: flub, GitHub: flub):


fix issue499: document selecting tests by node ID

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug problem that needs to be addressed type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

No branches or pull requests

1 participant