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
hiring-french
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
x

xenomachina

06/26/2020, 9:38 PM
Is there a simple way to run an individual Spec from IntelliJ? This works on a previous version of our code base that used kotlintest 3.4.2, but with kotest 4.1.0 the finest-grained thing I can run from IntelliJ seems to be the entire package which contains many specs. I tried installing the kotest plugin (1.0.2, which says it's for 4.1.0) and restarting IntelliJ, but I still get no "Run" options on individual specs.
s

sam

06/26/2020, 11:02 PM
Sounds odd. With 1.0.2 and 4.1.0 you should see the play icons on every test.
are you sure the project doesn't have 3.4.2 deps lurking about
x

xenomachina

06/26/2020, 11:07 PM
$ ./gradlew dependencies | egrep 'ko(tlin)?test' | sed -e 's:^.*- io\.:io.:' -e 's: .*::' | sort -u
io.kotest:kotest-assertions-core-jvm:4.1.0
io.kotest:kotest-assertions-shared-jvm:4.1.0
io.kotest:kotest-common-jvm:4.1.0
io.kotest:kotest-core-jvm:4.1.0
io.kotest:kotest-extensions-jvm:4.1.0
io.kotest:kotest-property-jvm:4.1.0
io.kotest:kotest-runner-junit5-jvm:4.1.0
s

sam

06/26/2020, 11:07 PM
You'll need io.kotest:kotest-runner-console-jvm:4.1.0 as well
but that shouldn't stop the icons from appearing though
x

xenomachina

06/26/2020, 11:16 PM
I added
testImplementation "io.kotest:kotest-runner-console-jvm:4.1.0"
to my dependencies, and reimported gradle in IJ, but still don't see any play icons. Where should they be?
I looked at the one where it was working, and I see what you mean by play icons. Yeah, they don't show up when we're using 4.1.0.
I just tried an intermediate version of our code, where we first switched from kotlintest to kotest, and that works. That was 4.0.6. Going to see if I can pinpoint exactly where it stopped working...
s

sam

06/26/2020, 11:44 PM
Ok thanks
x

xenomachina

06/27/2020, 12:34 AM
So far it's looking like it stopped showing the run and debug options on specs right when we moved from kotest 4.0.7 to kotest 4.1.0.
Yes, if I checkout the earliest version where it doesn't work, and change the kotest version back to 4.0.7 I start getting run+debug options on specs in IntelliJ, but if I change the version back to 4.1.0 then run+debug disappear from specs.
s

sam

06/27/2020, 12:46 AM
Which version of intellij
x

xenomachina

06/27/2020, 12:48 AM
2020.1.1 CE
j

johnaqel

06/29/2020, 4:50 AM
Same happened for me when I upgraded kotest to 4.1.0. Running on Ultimate 2020.1.
s

simon.vergauwen

06/29/2020, 9:00 AM
@sam just to let you know. I’m still seeing a lot of weird behavior as well in 4.1.0, that I didn’t see with plugin
0.9.3
and
4.0.6
.
s

sam

06/29/2020, 12:48 PM
The plugin shouldn't have even worked with 4.0.6 at all. If you were clicking the green run icon on the classname then that was coming from junit.
s

simon.vergauwen

06/29/2020, 12:49 PM
Also plugin
0.9.3
from before the official plugin release? 😮
s

sam

06/29/2020, 12:49 PM
Yep
s

simon.vergauwen

06/29/2020, 12:49 PM
Strange. That worked great for me.. 😅
s

sam

06/29/2020, 12:49 PM
The plugin was always designed for 4.1 snapshots
It needed classes that weren't in 4.0.x
The run icon at the class level?
s

simon.vergauwen

06/29/2020, 12:50 PM
I’m seeing a lot of weird things with 4.1.0 and the plugin. Just did a reboot, updated of IDEA, invalidate & restart caches, and re-import Gradle. And ended up here again. https://kotlinlang.slack.com/archives/CT0G9SD7Z/p1593071281019200
I even cleaned up old IDEA folders 😕
s

sam

06/29/2020, 12:51 PM
Before you upgraded where was the run icon
s

simon.vergauwen

06/29/2020, 12:51 PM
On individual tests and on the class
That’s the latest one I can find in my downloads folder, so that must be the one I was using before upgrading.
s

sam

06/29/2020, 12:53 PM
Right. And now you don't see the icons at all.
s

simon.vergauwen

06/29/2020, 12:53 PM
I see icons everywhere, but can’t run anything after restart/reset. And earlier it wasn’t properly rebuilding and never picked up any new changes.
(CLI worked fine)
s

sam

06/29/2020, 12:54 PM
Can you create an issue and paste in a screen shot of the run config that's created when you try to run a nested test
s

simon.vergauwen

06/29/2020, 12:54 PM
Alright, will do 👍
s

sam

06/29/2020, 12:54 PM
And also run with env var KOTEST_DEBUG=true
s

simon.vergauwen

06/29/2020, 12:54 PM
👍
s

sam

06/29/2020, 12:54 PM
And add std out to the issue
Finally paste in the exact intellij version from the about box
I'll match the version. I'm on linux though
s

simon.vergauwen

07/01/2020, 7:37 AM
@sam sad to report back it’s flaky. When I was trying to run with
KOTEST_DEBUG=true
, after I did my own series of rebooting/restarting/invalidating caches/re-importing it seemed to work again yesterday. If I can figure out a more reliable/reproduce-able scenario then I’ll create a ticket with the suggested scenarios.
Sorry I am unable to provide more info atm 😕
s

sam

07/01/2020, 11:47 AM
The log itself will be useful to me
👍 1
s

simon.vergauwen

07/01/2020, 12:50 PM
I just got an update of the plugin. Was that related to this? Can I follow the changes of the plugin somewhere?
s

sam

07/01/2020, 12:56 PM
There were a couple of bugs fixed but I don't think anything related to this
👍 1
s

simon.vergauwen

07/03/2020, 8:10 AM
Encountered it again today on a fresh instal of IntelliJ Ultimate. https://github.com/kotest/kotest/issues/1542