Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
This would run all tests which don't have the
This would run all tests that have the
Also, it looks like we silently remove/ignore tags that are not single_words with this line of code:
We should probably put warnings on tag names that are not valid (before we filter them out).
This is due to:
I support @pesse 's approach of adding "minus" as a prefix to the tags for the tests that must be excluded:
Yes, as to me this is correct. Consider a use case scenario: test case is marked as
and other test cases have other tags or have no tags at all.
then I expect that will be executed ALL test cases EXCEPT those marked with "long_running" tag.
then I expect that will be executed ALL test cases EXCEPT those marked with "long_running" tag PLUS those that marked with "wip".
In a conflict situation, when we have intersecting sets:
and when we call:
then I expect that will be ALL test cases EXCEPT those marked with "long_running" tag PLUS those that marked with "wip" EXCEPT those marked with "long_running" again. I.e. in example above will be run only
But now this MY expectation goes against the "OR" rule of annotations (http://utplsql.org/utPLSQL/v3.1.7/userguide/annotations.html):
That's why I'd considered a change to the "OR" rule for annotations and made it this way:
What would you say?
I would say:
and when we call
This is because of the exclusion logic.
So we say:
When you combine filtering by suitepath and filtering by tag