I have a test suite that uses multiple junit engines, and when i run tests by uniqueId kotest also r...

# kotest

[christophsturm]

I have a test suite that uses multiple junit engines, and when i run tests by uniqueId kotest also runs tests even when the uniqueId clearly states a different engine than kotest. [engine:failgood]/[class:...]/[class:...]
I think kotest should just run no tests when the uniqueid selector is used with a different engine.

[sam]

Can you put the version of kotest you are using on this ticket please https://github.com/kotest/kotest/issues/2806

[christophsturm]

done, thanks!

[sam]

I thought you'd have fully migrated to failgood by now 🙂

[christophsturm]

we have some kotests fans on the team and I learnt a lot of great things about kotest already. on the other hand we have tests written in all different kotest styles which is a bit confusing (at least to me)

[sam]

Ah that's cool. I know you're not a fan of the multiple styles. I think its a strength

[christophsturm]

I just see that its very confusing for some of my coworkers who are not so experienced with writing tests.

[sam]

Fair enough. I say that's on team though to mandate a style.

[christophsturm]

one other aspect thats important to me is also that all those options are bad for stability. I think every branch in a codebase is bad for stability, everyone should run the exact same code.

[sam]

Yeah, the styles all end up in the same model. Specs -> Containers -> Tests

[sam]

You could build your failgood style on top of kotest for example

[christophsturm]

yeah, but one think i really like about failgood is that its own test suite runs in <1 second

[sam]

ha, irrelevant to users tho