Is there any way to mock a extension function with Mockito?

The send is being called by my SUT and the test is on the return of the function calling send in the SUT.

I believe it is not Spek-related discussion anymore.

should work, please make sure everything JUnit platform related is on 1.0.0 and JUnit Jupiter related is on

5.0.0

. Also you can try to kill/start Gradle daemon just in case

hey @raniejade beta 7 dropped today, do you think the file copy in test builds bug is fixed?

i need it for robolectric

I’ll probably just use JUnit 5 alone. I’ve had this debugging issue for about a week now (ever since i’ve tried to start using it) and have yet to have successful output with the intellij plugin. It’s a cool library otherwise

can you check the code?

Oh, do I need to target Java 8?

nvm... apparently Spek with Android doesn't support JUnit 5

does anyone have any examples of spek in a MASSIVE project? I'm just wondering how well spek converts from small open-source projects to a project with hundreds of thousands of lines of code.

https://github.com/spekframework/spek/issues/286 - still issues with multiple class loaders. i added an example how is this working in java 8 and junit 4 based specification framework. please check whenever you are free.

Isn't it enough to just reset it with the factory in afterEachGroup? I'm just trying to understand the implementation to know what to expect...

But unlike the stock JUnit-based setup, makeRedisHandler in the Spek instance fails because it claims it cannot get the container IP or port until the container is started.

@raniejade anything? does spek work with the AS3 RC?

Are there limitations around using annotations for Spek test classes? I'm trying to leverage

com.github.trevershick.test.ldap

, which can take an annotation to additionally configure the LDAP instance. This annotation works fine in JUnit (4 and 5) based tests, but appears to break with Spek.

@LdapConfiguration(ldifs = arrayOf(Ldif("/hoyluPersonTestSchema.ldif")))
class LdapHandlerSpec : Spek({
    val ldapServer = LdapServerResource(this)

@codeslubber if you are interested, I managed to run Paulina's sample on AGP 3.0 https://github.com/sgrekov/hangman/commit/724040abd9b73cc9cd56d44f19efe77ed24317e4

This doc doesn’t work https://github.com/spekframework/spek/blob/e659eb633928f74cc52480e734ab6155dc310656/documentation/src/asciidoc/setting-up.adoc#setting-up-android

where should I look?

I get:

WARNING: TestEngine with ID 'spek' failed to discover tests

stacktrace:

Nov 06, 2017 7:19:28 AM org.junit.platform.launcher.core.DefaultLauncher handleThrowable
WARNING: TestEngine with ID 'spek' failed to discover tests
java.lang.IllegalAccessError: tried to access method org.junit.platform.engine.support.descriptor.ClassSource.<init>(Ljava/lang/Class;)V from class org.jetbrains.spek.engine.SpekTestEngine
	at org.jetbrains.spek.engine.SpekTestEngine.resolveSpec(SpekTestEngine.kt:114)
	at org.jetbrains.spek.engine.SpekTestEngine.resolveSpecs(SpekTestEngine.kt:80)
	at org.jetbrains.spek.engine.SpekTestEngine.discover(SpekTestEngine.kt:50)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:130)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:117)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:90)
	at org.jetbrains.spek.tooling.runner.junit.JUnitPlatformSpekRunner.run(JUnitPlatformSpekRunner.kt:107)
	at org.jetbrains.spek.tooling.MainKt.main(Main.kt:58

pom.xml

<dependencies>
        <dependency>
            <groupId>org.jetbrains.kotlin</groupId>
            <artifactId>kotlin-stdlib-jre8</artifactId>
            <version>${kotlin.version}</version>
        </dependency>
        <dependency>
            <groupId>org.jetbrains.kotlin</groupId>
            <artifactId>kotlin-reflect</artifactId>
            <version>${kotlin.version}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.spark</groupId>
            <artifactId>spark-core_2.11</artifactId>
            <version>2.2.0</version>
        </dependency>
        <dependency>
            <groupId>com.github.jkcclemens</groupId>
            <artifactId>khttp</artifactId>
            <version>master-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>org.knowm.xchart</groupId>
            <artifactId>xchart</artifactId>
            <version>3.5.0</version>
        </dependency>
        <dependency>
            <groupId>org.jetbrains.spek</groupId>
            <artifactId>spek-api</artifactId>
            <version>1.1.5</version>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>org.jetbrains.spek</groupId>
            <artifactId>spek-junit-platform-engine</artifactId>
            <version>1.1.5</version>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>org.amshove.kluent</groupId>
            <artifactId>kluent</artifactId>
            <version>1.30</version>
        </dependency>
        <dependency>
            <groupId>org.junit.platform</groupId>
            <artifactId>junit-platform-runner</artifactId>
            <version>1.0.0</version>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.12</version>
        </dependency>
    </dependencies>

My test is in

src/test/kotlin

object Test: Spek({
    describe("a calculator") {

        it("should return the result of adding the first number to the second number") {
            "test" shouldEqual "test"
        }

        it("should return the result of subtracting the second number from the first number") {
        }
    }
})

Hey guys, the problem that was happening with AndroidStudio3.0 is still happening?

why do you want that? The only valid answer is: "action is too expensive" 🧌

Junit 5 fixed a few of those issues (such as description, nested classes, extensions). Unfortunately it will take forever to become a standard. The session was really insightful.

@artem_zin I have a question for you that intrigues me the most Have you tried

kotlin-test

? The argument "spek was hold on jetbrains repo" sounds weak. Very interested if you have any experience with it. I personally consider kotlin-test as the main alternative to spek/spock/etc. And to writing own testing lib, of course 😂

@dsgryazin If I may join 😉 I’ve tried and it was cool but it wasn’t sufficient because it didn’t allow to have unlimited nesting of test cases. On the other hand it was very easy to write custom Specification which does based on its based specification class. (But it performed poorly)

Hi! I would like to use Spek as a drop-in replacement for JUnit, but the configuration instructions that I've found insist on replacing the test runner. Is there a way to run spek without its runner?

One small detail I can't get to be perfect yet:

on("1122") {
    val input = "1122"
    val result = taskA(input)

    it("should produce 3") {
        assertEquals(3, result)
    }
}

As you see, there are unfortunate repetitions of the input value and the assert value if I want to use them in the section names. How do you tackle that?

@raniejade is this the same bug? https://stackoverflow.com/questions/45819700/android-studio-3-0-gradle-3-0-0-beta2-breaks-kotlin-unit-test-coverage

We are prototyping a special DSL highlighting that hides the “syntax” highlighting and provides an option to have a custom highlighting on a DSL. What would be Spek functions to consider a top level DSL to highlight? We’d like to experiment with it. /cc @pavel.talanov