A modern programming language that makes developers happier.

kotlinlang

Great Talk on KotlinConf about TestBalloon, <@U54CM9PGS>! Really got inspired to rework some of my tests immediately! But, sadly, I already fail to get the Plugin installed (tried version 1.0.0 and 1.0.1), but they are not available on Maven Central or Gradle Plugin Repository... how do I get this plugin and lib? And another question on the documentation: why do you declare the test balloon frame work as a normal dependency and not a test dependency?
Thanks!

Did you check the Release Notes? There is a table with the available versions matched to Kotlin releases.

Where exactly does the documentation specify a non-test dependency?

Hi <@U54CM9PGS>, well generally, I wanted to start with "Getting started", that is, install the Plugin, add dependency to framework. No, I did not yet read release notes... I hoped Getting started gets me started.

For the plugin, I get an error:
```- Plugin Repositories (could not resolve plugin artifact 'de.infix.testBalloon:de.infix.testBalloon.gradle.plugin:1.0.1')
  Searched in the following repositories:
    Gradle Central Plugin Repository
    MavenRepo```
As for the dependency, it's a little bit ambiguous, as the context is missing. But getting started shows this:
```dependencies {
    implementation("de.infix.testBalloon:testBalloon-framework-core:$testBalloonVersion")
}```
Normally, in a "simple" project with only one dependency block, I would prefer this to be `testImplementation` instead of `implementation`...

But now I see... the version should be something like 1.0.1-K2.3.20

Sorry, but this should be mentioned in "Getting Started", I guess...

And for the dependency, do I also use this version tag? Or is that simply 1.0.1?

Coming from Kotest this is unusual, that's why I did not spend a second to look other than in Getting Started... :slightly_smiling_face:

And the dependency notation above is for the Kotlin Multiplatform Gradle plugin. With JVM-only, it’s indeed `testImplementation`.

image.png

Kotest does not provide backports down to Kotlin 2.0 for the latest version.

While I got you answering so quickly: anything special that I need to be careful with now that I have some old JUnit tests, 95% Kotest Funspecs and now the first testBalloon? I wanted to convert the old JUnit ones with testBalloon to get into it... :wink:

Do it step by step. Use TestBalloon where it has the greatest impact. Keep your old tests where it doesn’t matter as much. Once you become acquainted with TestBalloon, you might want to switch over completely but you don't have to rush.

Thanks for pointing out the documentation deficiencies. Created two issues for tracking and informing other folks.