-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Colon-pair keywords #806
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
Colon-pair keywords #806
Conversation
… to simplify copy/pasting from test output.
…"colon pairs" keywords.
…with "-k" argument.
OK my bad, python2.6 doesn't accept re.sub(..., flags=xxx) argument. |
Related to #765 |
So continuing the conversation from the original bitbucket PR, does it help if -k understands the node-id? The whole point of the node-id was that it could be copy-pasted, partially copy-pasting it seems like a weird use-case and increases the backwards-compatibility someone who'd like to tackle the python keywords issue with -k would have to worry about. |
I'm -1 on this one, test ids can be passed without -k |
Imho We should support exact full name prefix matching and regex matching via the planned keyword expressions |
I was +1 on the PR until I found out that you can actually copy/paste ids directly, but now I must say I'm +0 on it as I agree with @flub's points. |
we should take a look at partial test id's for the following use-case: -> run all parametrizations of a test functions |
But as part of -k? I think that should be part of the normal test id
|
yes, it should be part of the test id selection i suspect a reorganization of collection<>parametrisation will do some good, |
So it seems like the consensus is that selection by ID is already suitably covered and should not be done by -k. Thanks for submitting the pull requests anyway! |
Here is the port to GitHub of that previous pull request : https://bitbucket.org/pytest-dev/pytest/pull-request/305/allow-selection-with-myfilepy-myfile/diff#comment-7531336