I m seeing some weird behavior with plugin 1 0 2 and Kotest kotlinlang #kotest

Channels

kotlin-foundation

compose-android

ohio-kotlin-users

kotlin-by-example

sofl-user-group

kotlin-multiplatform-contest

tricity-kotlin-user-group

kotlin-in-action

android-databinding

cincinnati-user-group

fluid-libraries

codemash-precompiler

kotlingforbeginners

jhipster-kotlin

prozis-android-backup

realworldkotlin

graviton-browser

spring-security

domain-driven-design

connect-audit-events

swiss-user-group

effectivekotlin

refactoring-to-kotlin

russian-kotlinasfirst

androidgithubprojects

introduce-yourself

pocketgitclient

effective-kotlin

algolialibraries

lambdaworld_cadiz

intellij-tricks

kotlin-pakistan

navigation-architecture-component

strife-discord-lib

machinelearningbawas

leedskotlinusergroup

stayhungrystayfoolish

kotest-contributors

practical-functional-programming

swagger-gradle-codegen

100daysofkotlin

kotlinultimatechallenge

pattern-matching

kotlinforbeginners

competitive-programming

compose-ui-showcase

competitivecoding

kotlin-data-storage

skia-wasm-interop-temp

java-to-kotlin-refactoring

event21-community-content

androidx-xprocessing

embedded-kotlin

fb-internal-demo

image-processing

myndocs-oauth2-server

kotlintest-devs

beepiz-libraries

kotlinprogrammers

cscenter-course-2016

k2-early-adopters

intellij-plugins

language-proposals

library-development

refreshversions

language-evolution

kotlinx-datetime

framework-elide

compose-desktop

jvm-ir-backend-feedback

android-architecture

100daysofkotlin-2021

github-workflows-kt

python-contributors

squarelibraries

arrow-contributors

codingconventions

getting-started

Title

s

simon.vergauwen

06/25/2020, 7:48 AM

I’m seeing some weird behavior with plugin 1.0.2 and Kotest 4.1.0. Now it’s not picking up new tests, and when I rebuild I cannot run the suites (see attached log). Yesterday when I first upgraded I ran into the same, but without having it work first. But it strangely started working for me after a couple restarts/clearing caches. However it already re-appeared this morning.

s

sam

06/25/2020, 12:04 PM

It's like the jar isn't on the classpath. I guess a build inside intellij fixes it temporarily?

w

wasyl

06/25/2020, 1:06 PM

Perhaps syncing with Gradle would help? This happens so often with Android/Robolectric/JVM unit tests in Android Studio

s

simon.vergauwen

06/26/2020, 9:39 AM

This happens so often with Android/Robolectric/JVM unit tests in Android Studio

I’m writing vanilla Kotlin with only a dependency on Kotlin JDK8 in IntelliJ 😕

Gradle sync didn’t help.

Rebuilding inside IntelliJ also doesn’t temporary fix it. It’s still persisting today.

Found the culprit. I’ve ran into this before where plugins interact with Gradle, and cache updates are written to IntelliJ due to this config. (I see it change randomly, since I always set it to Gradle).

Changing it to Gradle fixes the issue.

Although I now see it again not picking up new tests.

5 Views

#kotest Join Slack