kotlinlang #spek

INFO: Discovered TestEngines with IDs: [spek, junit-jupiter]
Running sample.SampleSpec
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec <<< FAILURE! - in sample.SampleSpec
JUnit Jupiter  Time elapsed: 0.01 sec  <<< FAILURE!
null

snowe

04/27/2017, 8:25 PM

with your spek

snowe

04/27/2017, 8:25 PM

Copy code

class SampleSpec : Spek({
    given("some context") {
        on("executing some action") {
            it("should pass") {
                assertEquals(2, 2)
            }
        }
    }
})

snowe

04/27/2017, 8:32 PM

@hhariri looks like jupiter is trying to run every test a second time. Any way to stop that?

thanh

04/30/2017, 2:29 AM

any one success with Android Junit 5? I tried with https://github.com/aurae/android-junit5 but no success so far.

hhariri

05/03/2017, 11:49 AM

1.1.1 with the fix for JUnit M4 is now available on bintray and maven.

🎉 4

metal 1

K 3

robfletcher

05/08/2017, 4:34 PM

Are the

subject

and

itBehavesLike

features mentioned here http://spekframework.org/docs/latest/#_subjects part of a future release? I don’t see them in the 1.1.1 API

robfletcher

05/08/2017, 11:02 PM

never mind, I see it’s a separate extension jar.

raniejade

05/11/2017, 12:07 AM

If anyone is having problems running specs in idea with spek 1.1.1, please add

org.junit.platform:junit-platform-launcher:1.0.0-M4

in your test classpath.

jmfayard

05/12/2017, 5:43 AM

@jmfayard has left the channel

jackmiras

05/12/2017, 7:47 PM

Hi guys, I'm working on a web API that uses Kotlin and Spek and every time that I try to build my project using Gradle I'm getting the following error:

Copy code

Exception in thread "main" java.lang.AbstractMethodError: Method org/jetbrains/spek/engine/Scope$Group.getType()Lorg/junit/platform/engine/TestDescri
ptor$Type; is abstract                                                                                                                               
        at org.jetbrains.spek.engine.Scope$Group.getType(Scope.kt)                                                                                   
        at org.junit.platform.launcher.TestIdentifier.from(TestIdentifier.java:60)
        at org.junit.platform.launcher.TestPlan.lambda$from$0(TestPlan.java:78)
        at org.junit.platform.engine.TestDescriptor.accept(TestDescriptor.java:245)
        at org.junit.platform.engine.TestDescriptor.lambda$accept$0(TestDescriptor.java:247)
        at java.lang.Iterable.forEach(Iterable.java:75)
        at org.junit.platform.engine.TestDescriptor.accept(TestDescriptor.java:247)
        at org.junit.platform.launcher.TestPlan.lambda$from$1(TestPlan.java:79)
        at java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:608)
        at org.junit.platform.launcher.TestPlan.from(TestPlan.java:79)
        at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:130)
        at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:87)
        at org.junit.platform.console.tasks.ConsoleTestExecutor.executeTests(ConsoleTestExecutor.java:65)
        at org.junit.platform.console.tasks.ConsoleTestExecutor.lambda$execute$0(ConsoleTestExecutor.java:57)
        at org.junit.platform.console.tasks.CustomContextClassLoaderExecutor.invoke(CustomContextClassLoaderExecutor.java:33)
        at org.junit.platform.console.tasks.ConsoleTestExecutor.execute(ConsoleTestExecutor.java:57)
        at org.junit.platform.console.ConsoleLauncher.executeTests(ConsoleLauncher.java:79)
        at org.junit.platform.console.ConsoleLauncher.execute(ConsoleLauncher.java:69)
        at org.junit.platform.console.ConsoleLauncher.main(ConsoleLauncher.java:41)
:junitPlatformTest FAILED

Does anyone knows how can I solve or work around this problem in order to make the build process works properly?

05/12/2017, 8:00 PM

@jackmiras you can try this https://kotlinlang.slack.com/archives/C0BE6KSRW/p1494461256755437

jackmiras

05/12/2017, 10:42 PM

@jk I realize that the version of Spek that I was using was the 1.1.0 and when a change to 1.1.1 things start working properly... Thanks for the heads up!

👍 2

carlw

05/13/2017, 12:41 PM

hi. i'm running spec successfully from gradle, but i'd like to use the debugger. i have the spek plugin installed, but am getting this when I create a Run Configuration in IntelliJ Exception in thread "main" org.junit.platform.commons.util.PreconditionViolationException: Cannot create Launcher without at least one TestEngine; consider adding an engine implementation JAR to the classpath at org.junit.platform.commons.util.Preconditions.condition(Preconditions.java:207) at org.junit.platform.launcher.core.DefaultLauncher.<init>(DefaultLauncher.java:52) at org.junit.platform.launcher.core.LauncherFactory.create(LauncherFactory.java:42) My build file is based on the user guide with the following dependencies addition. testRuntime 'org.junit.platformjunit platform launcher1.0.0-M4'

robfletcher

05/13/2017, 3:06 PM

It seems like

SubjectSpek

is pretty broken right now. When the spec is re-used with

itBehavesLike

the tests themselves use the subject from the original so while it looks like things are working, it’s actually testing the wrong class! Also

on

and

it

get different instances when using the

subject

property so tests can only be very simplistic. Is this known and still under development or should I file an issue on GitHub?

robfletcher

05/13/2017, 3:06 PM

Example:

Copy code

object JavaQueueSpec : SubjectSpek<Queue<String>>({
  subject { LinkedList() }

  describe("whatever") {
    on("pushing an item") {
      println("subject is a ${subject.javaClass} ${System.identityHashCode(subject)}")
      subject.offer("Hi")
    }

    it("can get popped") {
      println("subject is a ${subject.javaClass} ${System.identityHashCode(subject)}")
      subject.poll() shouldEqual "Hi"
      subject.poll() shouldEqual null
    }
  }
})

object ArrayDequeSpec : SubjectSpek<ArrayDeque<String>>({
  subject { ArrayDeque() }

  itBehavesLike(JavaQueueSpec)
})

robfletcher

05/13/2017, 3:07 PM

The

System.identityHashCode

reported in

on

and

it

are different (although consistent if invoked multiple times in that context). Also

ArrayDequeSpec

reports that its subject is actually a

LinkedList

robfletcher

05/13/2017, 3:09 PM

In fact if I change

ArrayDequeSpec

to have

subject { throw IllegalStateException() }

it still runs “successfully”

robfletcher

05/13/2017, 3:11 PM

This would be an incredibly useful feature to me as I have a scenario where I’m testing multiple implementations of an interface. I can do so by extending an abstract

Spek

but it’s not easy to add additional tests in the sub-classes for any non-shared behavior.

raniejade

05/13/2017, 4:14 PM

@carlw you have to add

testRuntime 'org.jetbrains.spek:spek-junit-platform-engine'

raniejade

05/13/2017, 4:15 PM

@robfletcher I'll take a look at it.

raniejade

05/13/2017, 4:20 PM

@robfletcher try adding a caching mode when you create the subject:

subject(CachingMode.GROUP) { ... }

raniejade

05/13/2017, 4:20 PM

by default each test/action (

it

on

) will have a unique instance

robfletcher

05/13/2017, 4:24 PM

ah, ok, I wasn’t aware of that.

robfletcher

05/13/2017, 4:25 PM

What about the situation with

itBehavesLike

using the wrong subject?

raniejade

05/13/2017, 4:27 PM

Yeah, it's a bug. trying to figure out the problem

robfletcher

05/13/2017, 4:29 PM

👍

carlw

05/13/2017, 4:35 PM

@raniejade thanks for looking into this. my problem was the wrong classpath module (_main instead of _test). the Run Configuration is working for me with the debugger

raniejade

05/13/2017, 4:43 PM

no worries, let me now if you have more problems.

robfletcher

05/13/2017, 4:45 PM

@raniejade

CachingMode.GROUP

works perfectly, thanks.