https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
n

Niko

12/17/2021, 8:06 AM
I'm having issues with the latest versions of Kotest (5.0.2) with IDEA (2021.3) and plugin (1.1.49-IC-213-EAP-SNAPSHOT), and Kotlin 1.6.0: Some time ago, everything was fine and dandy, but then something changed (it was either IDEA update, me changing the project, or upgrading Gradle or Kotlin version changed), and first I started having problems with running individual tests (like Ross wrote earlier). Then, again something changed, and now I'm able to run the tests via IDEA's Run <test class>: <test> gutter icon of individual tests launching the Kotest runner panel, but the Run <test class> now simply launches a Gradle build, no tests run. IDEA's Gradle > project > verification > test runs no tests, nor does running
./gradlew test
. Currently, I have a root project with multiple subprojects (modules), and I'm applying some conventions (like applying Kotest) to all the subprojects using a Gradle plugin. I'm wondering, if this setup has somehow screwed up the discovery (more in thread)
Also, • I've removed
.gradle
and
build
dirs, no effect • Running
./gradlew dependencies
lists all Kotest deps correctly This is the part in the plugin, that applies Kotest:
private fun initTesting(project: Project) = project.run {
    <http://logger.info|logger.info>("Setting up testing for the project (kotest ${Versions.kotestVersion})")

    tasks.withType<Test>() {
        useJUnitPlatform()
    }
    // TODO: combine with above?
    val test by tasks.getting(Test::class) {
        // bootstrap Kotest system properties (-Dx=y) to enable targeting test tags
        // via CLI: <https://kotest.io/docs/framework/tags.html>
        systemProperties = System.getProperties()
            .map { it.key.toString() to it.value }.toMap()
        // TODO: once the build script moves forward from 1.4.31, migrate to
        //  .associate {}
    }

    dependencies {
        add("testImplementation", Dependencies.kotestRunner)
        add("testImplementation", Dependencies.kotestAssertionsCore)
    }
}
s

sam

12/17/2021, 8:13 AM
When you run a class does intellij appear to run but just no tests appear?
n

Niko

12/17/2021, 8:17 AM
Correct. Class (
StringSpec
) > Run '<class>' Ctrl+Shift+F10 > IDEA shows the Run panel with which seems to be a Gradle run config, and not a Kotest one (I'm guessing the Gradle runner should delegate the test execution somehow to Kotest..?)
But when running individual tests via gutter icon, all's as expected:
s

sam

12/17/2021, 8:41 AM
can you clean the build, run the class (so via gradle), and check the build folder after, see if a test report is generated
n

Niko

12/17/2021, 8:45 AM
Also the HTML file for the class seems to contain both the tests run and passed
s

sam

12/17/2021, 8:46 AM
so they're being run
you're just not seeing the output in intelli
n

Niko

12/17/2021, 8:47 AM
Looks like it
s

sam

12/17/2021, 8:47 AM
I have since something similar
it's like sometimes intellij doesn't open the "tests" window
n

Niko

12/17/2021, 8:52 AM
I don't think it's only IDEA though, since running
gradle clean test
in terminal will also run the tests in silence, and only report build failure if I make a test fail:
> Task :test

dev.niko.sc.LoadFactorsTest > all load factors detected FAILED
    java.lang.AssertionError at LoadFactorsTest.kt:23
        Caused by: java.lang.AssertionError at LoadFactorsTest.kt:23

19 tests completed, 1 failed

> Task :test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> There were failing tests. See the report at: file:///.../sc/build/reports/tests/test/index.html

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at <https://help.gradle.org>

BUILD FAILED in 11s
26 actionable tasks: 5 executed, 21 up-to-date
I remember previously seeing a terminal output of the Kotest runner itself..?
s

sam

12/17/2021, 8:53 AM
not unless you configure gradle to output tests, and if your only line is useJUnitPlatform then it won't
maybe that's what you need
I have this
tasks.named<Test>("test") {
   useJUnitPlatform()
   testLogging {
      showExceptions = true
      showStandardStreams = true
      exceptionFormat = TestExceptionFormat.FULL
   }
}
And here is the run configuration for a test after I have ran it at the class level, what does yours look like ?
n

Niko

12/17/2021, 8:57 AM
setting the
testLogging {}
, now the assertion errors are printed, but no other changes (it's a start). Previously I remember running the class for tests would create a Kotest run config, and bring up the Kotest panel, and not the Gradle run config one
s

sam

12/17/2021, 9:01 AM
That's because intellij changed the default in 2021.3
You can change it back here:
n

Niko

12/17/2021, 9:03 AM
Right... So it would be IDEA "issue" after all...
s

sam

12/17/2021, 9:05 AM
well I guess them changing the default possibly, but it should work with gradle anyway, and does for me
The underlying issue seems to be that under certain circumstances, intellij doesn't realise the task you are running is a "Test" task and doesn't switch the run window to be a tests output window
n

Niko

12/17/2021, 9:06 AM
It does..? Damn. Well, changed it to run tests with IDEA, now I'm getting the Kotest panel atleast for some proper test cases
s

sam

12/17/2021, 9:07 AM
So I guess you can just do it that way
the kotest plugin is better anyway, as you'll be able to navigate to tests properly
gradle doesn't do it properly because its implementation of junit5 is broken
n

Niko

12/17/2021, 9:07 AM
☝️ true that
Yeah, there seems to be some issues with the Gradle Kotlin build scripts (I'm having some red squiggly with applying some of the project configs as IDEA cannot handle the SAM interfaces of the build script builders and mis-identifies this/it with the scopes...) so no wonder if under some circumstances the process fails with IDEA as well
s

sam

12/17/2021, 9:09 AM
yeah possibly
n

Niko

12/17/2021, 9:10 AM
But that fixes the main issue of not getting proper reporting thanks Sam. I'll check back in a year or so, whether the tests runner option could be re-changed as Gradle...
😂 1