Replies: 1 comment
-
|
One alternative you could look at would be registering a It has the same semantics as filtering by tags. The tests are removed from the test plan unlike the execution edition where tests are kept but then skipped. Unfortunately filters don't have access to the original tag expressions so you'd still have to check an environment variable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So this is a bit of an api puzzler for me - I'd like to have several custom annotation test groups, say
@Weeklyand@Nightlywhich are disabled by default. I can meta-annotate them with the corresponding@Tagbut this then relies on the build system's configuration to exclude those tags. It's not exactly what I want - I'd like any launcher (IDEs, gradle, maven) to see those tests as disabled by default (unless their tags are explicitly included), without any additional configuration.Is this even possible?
For now I've opted to implement the above using a layered
ExecutionConditionthat looks at a system property, so something like this:where
TagStateis:I wonder if I'm missing any other implementation routes. Or maybe something obvious that just eluded me. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions