in the new one I didn't notice any, and forgot to try on the old one. Now after factoring out like you suggested, I don't have any lags

@dimsuz: thank you very much, Dmitry, you helped us uncover a really annoying performance problem, which when fixed can improve life for almost every Kotlin developer 👍 K

wow, glad to be of help.

Looking into using Spek, anyone know what the latest version is? I tried

1.0.25

but it complains that my kotlin version

1.0.3

differs from my test app (

1.0.2

) so I assume spek isn’t up to date with kotlin?

@john.shelley: The latest snapshots from the current master are here https://jetbrains.jfrog.io/jetbrains/spek-snapshots

which is what we’re working on for the 1.0 release.

@john.shelley:

I tried

1.0.25

but it complains that my kotlin version

1.0.3

differs from my test app (

1.0.2

) so I assume spek isn’t up to date with kotlin?

I resolved this by explicitly specifying kotlin dependencies for test configuration, i.e.

testCompile rootProject.ext.kotlinRuntime // 1.0.3 version
  testCompile rootProject.ext.kotlinStdLib

(gradle build) This way it correctly resolves ambiguous dependencies

or

force

it

it’s problem of Android Gradle Plugin, it’s kind of warning that breaks build because it thinks that it’s important enough

@dimsuz: don’t you or others who use Spek experience that

xit/xon/etc

works in IDE but doesn’t work under Gradle

? It executes

x

tests…

@artem_zin: nope, didn't use it yet. I only used

fit

which was your hint, btw. Didn't know about

xit/xon

by the way these constructs are not mentioned in the docs at all, but it would be helpful to know about them (especially considering no IDE support for running a specific test)

@dimsuz:

x

allows you ignore part of the Spek tree, like

@Ignore

in JUnit. If it’s not hard, can you please check it?

@artem_zin: yep, same here. IDE ignores failing

xit

test, all pass, while

./gradlew test

executes it and fails

Damn… JB: can you please clarify if IntelliJ runs tests in Gradle project without invoking Gradle test tasks? Afaik the problem is that Gradle runs tests with own test runner, while IntelliJ only compiles code with Gradle and then runs tests on its own

I’m having problems running spek’s own tests on master. Running

gradle test

leads to

java.lang.NoSuchMethodError: org.junit.platform.launcher.listeners.TestExecutionSummary.getTotalFailureCount()J
…

Are there any ways around it?

whoa, Spek doesn’t have CI… That’s a shame for test framework…

It has: https://teamcity.jetbrains.com/project.html?projectId=Spek&tab=projectOverview

But @hhariri doesn’t seem to look there 😞

ah, @hhariri can you please attach build results to PRs on GitHub? (status of main branch in README would be great too)

@bamboo has left the channel

@orangy: what do you mean not look there?

@artem_zin: Yes. We will

@hhariri: I mean build failing since Jul 12, nothing else.

Ah that, yeah. It’s cause of some changes to Junit, but will be fixed.

But we do have CI from day one 🙂

@ilya.chernikov: should be fixed with the latest master 🙂 missed out some dependencies while upgrading JUnit 5.

@User uploaded a file:

@sonica has left the channel