The new release (and especially the new docs) insp...
# testballoon
p
The new release (and especially the new docs) inspired me to finally give testballoon a shot. We've been on kotest and the ide integration hasn't been working well lately so I was open to a change. Our favorite part of kotest was the matching so it's super cool to see that testballoon let us keep that! It was such a painless process migrating our first module that I went ahead and moved them all over. The only thing I miss from kotest is the lifecycle hook functions, but we were able to replace those with the
@TestRegistering
pattern with only a few rough edges. Historically we only ran tests in jvmTest because getting the other targets working in kotest was never working well. It was super smooth with testballoon so we moved most (not all, there are few that need jvm for other reasons) to commonTest and got multi-platform testing with little effort. All this to say, very nice work! Thanks for making such a great tool!
thank you color 1
o
Thanks for that great feedback! Actually, that's what I'm hearing repeatedly from folks who have migrated: They almost instantly roll out testballoon TestBalloon to all their projects. I'm curious about which lifecycle hooks you might be missing. There's a section on migrating from Kotest on the new doc site and some lifecycle hooks are covered there. If you have a use case that's not covered, please throw it at me and I'll try to figure out how to handle it.
p
I read those docs when I started but I must have misunderstood them at the time (probably just early-morning brain getting in the way). I just re-read them and the TestConfig pattern makes a lot more sense. I just tweaked the test suite that was a little hacky before and now it is all good. Thanks for reminding me about it
While I have you though, I've noticed that when I hit the run arrow in the gutter I am able to select which type of test to run, but on subsequent runs I don't see the options anymore (it just runs whatever the previous selection was). So I'm unsure how to change between them after an initial run. This caching seems to only be per arrow because if I hit another arrow in the same file I get the options again
I suspect there's probably an obvious step here I'm missing
o
Regarding the docs: If there is anything that did not come across easily enough, please tell me. That's always valuable when trying to improve them. The run gutters: That's actually an IntelliJ-IDEA-internal feature that works the same way with gutters from the Kotlin plugin: Once a run configuration is created for a gutter, is will be re-used. To stop that, delete the run configuration.
🙏 1
p
I don't think there was anything wrong in the docs, I was probably just reading too quick
🙂 1