I've finished migrating KtMongo from Kotest to Tes...
# opensavvy
c
I've finished migrating KtMongo from Kotest to TestBalloon. Some numbers that may be of interest; Protocol:
./gradlew clean; ./gradlew check; ./gradlew check --no-configuration-cache --rerun-tasks
clean
to ensure there aren't files left over •
check
to ensure everything needed is available locally (all dependencies are downloaded, etc) •
--no-configuration-cache
to ensure a fair execution order and disable intra-project parallelism •
--rerun-tasks
to disable incremental compilation, the build cache, up-to-date checks, etc • Only the last invokation is timed, using Gradle's build timer So: the test measures how long tests execute, but also how long it takes to compile, etc. The repository compiles to nearly all Kotlin targets using cross-compilation, so compilation time is quite a lot. Kotest: 2c899266a67a1c605e97d615afa353246859e261 • 2min 2s TestBalloon: 3dc162f411167345de9f38bd3c4cbb46569afa54 • 1min 2s That's a pretty big difference if you ask me!
o
That's cool! Which TestBalloon release was in use? The latest release 0.4.0, besides supporting incremental compilation, also dropped the last remnants of classpath scanning.
c
0.3.3-K2.2.0. I since updated to 0.4.0, but I changed a lot in the meantime (Gradle 8.14.3…) so it wouldn't be a fair comparison
👍 1