https://kotlinlang.org logo
#kotest
Title
# kotest
c

christophsturm

02/01/2022, 11:57 AM
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.
🎉 1
👍🏻 1
s

sam

02/01/2022, 1:44 PM
Can you put the version of kotest you are using on this ticket please https://github.com/kotest/kotest/issues/2806
c

christophsturm

02/01/2022, 2:14 PM
done, thanks!
s

sam

02/01/2022, 2:14 PM
I thought you'd have fully migrated to failgood by now 🙂
c

christophsturm

02/01/2022, 2:17 PM
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)
s

sam

02/01/2022, 2:18 PM
Ah that's cool. I know you're not a fan of the multiple styles. I think its a strength
c

christophsturm

02/01/2022, 2:19 PM
I just see that its very confusing for some of my coworkers who are not so experienced with writing tests.
s

sam

02/01/2022, 2:19 PM
Fair enough. I say that's on team though to mandate a style.
c

christophsturm

02/01/2022, 2:21 PM
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.
s

sam

02/01/2022, 2:21 PM
Yeah, the styles all end up in the same model. Specs -> Containers -> Tests
You could build your failgood style on top of kotest for example
c

christophsturm

02/01/2022, 2:27 PM
yeah, but one think i really like about failgood is that its own test suite runs in <1 second
s

sam

02/01/2022, 2:28 PM
ha, irrelevant to users tho
2 Views