Or perhaps I don't understand the idea of tags and am not using it correctly

However you can put tags on the spec itself

There's @Tag or @Tags can't remember which one. Put that on the spec and the entire spec will be skipped

I see both @Tag and @Tags

are you on 4.x ?

io.kotest.core.annotation.Tags

I will try 4.x

thanks a lot, much appreciated!

You might want to just jump straight to 4.1.0.RC2

4.1.0.RC2 

is it stable enough?

its just waiting on me adding a blog post

Tried the @Tags annotation. What I see is this: It works good if you explicitly exclude a tag (kotest.tags.exclude=Tag_A) in the test run. In this case the whole spec with @Tags("Tag_A") is skipped and beforeSpec is not executed. However, if you run with kotest.tags.include=Tag_B, then: • for test with no @Tags annotation, the test itself will be ignored, but the beforeSpec will be executed. • the test with @Tags("some_other_tag") will be ignored and its beforeSpec won't be executed.

Hey! Looks like the whole behaviour of

-Dkotest.tags.include=

parameter has been changed after I upgraded to 4.1.0 final. I have a base test that has a base tag for all the tests.

override fun tags(): Set<Tag> = setOf(MyTag)

Before the upgrade I could execute the tests with

-Dkotest.tags.include=MyTag

and the tests were executed. Now they are not executed and the test runner doesn't find any tests. It only finds a test if I use @Tags("MyTest") annotation. So looks like this parameter only works with annotations now and doesn't work when you create an io.kotest.core.Tag objects and override them in your test specs. Is this expected behaviour?

@sam please take a look above

Any estimates on this one?

I've started work on this and I'm kind of stumped as to how to get the required behaviour. Overriding tags in a spec was never intended to apply at the spec level. As the documentation states:

/**
 * Any tags added here will be in applied to all [TestCase]s defined
 * in this [Spec] in addition to any defined on the individual
 * tests themselves.
 */
fun tags(): Set<Tag> = emptySet()

So does the system need to inspect all the root tests, and skip the spec only if none of them are active.

where are you putting the kotest.tags.include, just inside the intellij run config ?

but gonna use it with gradle test task

It's looking for the tag on the Spec and finding it

then looking for the tag on the test as well

but it's not on the test, and there's no inheritance rules

There seems to be lots of edge cases here. I need to spend a day thinking through these rules. I'll probably have to deprecate the @Tags and come up with something else.

I'll see how junit does it

Just a reminder - my initial problem was to find a way to have a beforeSpec() thing executed after tests filtering by tags

Might be reasonable to always run prepareSpec

I guess if you want "all tests filtered out" to mean different things depending on the Spec class, then you would have to roll something yourself. Or perhaps it could be controlled in config.

My application under tests has different configurations, which means that I need to run different tests depending on core application configuration. These test may (or may not) have a common setup. I wanted to use Tags to distinguish these tests run and at the same time to have some common setups

Here is more detailed question. Please take a look, am I doing something wrong?

and it works with kotest plugin

My guess was that the problem was in system properties propagating to test executor, but I checked it and

kotest.tags.include -> MyTag

was in system properties

Double checked Seems like the -Dkotest.tags.include=ATag only works for @Tags(“ATag”) and doesn’t work for .config(tags = setOf(ATag)). Whereas -Dkotest.tags.exclude=ATag works fine.

4.1.2 has been released which should address all your issues. Thanks for the help diagnosing this.