kotlinlang #spek

given("A correct email adres") {

    beforeEach{ reset(mainView) }

    listOf("<mailto:test@appfoundry.be|test@appfoundry.be>", "<mailto:ttest@fffff.org|ttest@fffff.org>", "<mailto:bbbb@bbbbb.com|bbbb@bbbbb.com>").forEach {
        it("$it should be shown as email") {
            mainPresenter.processText(it)
            verify(mainView, times(1)).showItem(any<Item>())
         }
    }
}

simon.vergauwen

09/13/2016, 6:58 PM

That works fine.

simon.vergauwen

09/13/2016, 6:58 PM

Copy code

given("A correct email adres") {
    listOf("<mailto:test@appfoundry.be|test@appfoundry.be>", "<mailto:ttest@fffff.org|ttest@fffff.org>", "<mailto:bbbb@bbbbb.com|bbbb@bbbbb.com>").forEach {
        reset(mainView)
        it("$it should be shown as email") {
            mainPresenter.processText(it)
            verify(mainView, times(1)).showItem(any<Item>())
         }
    }
}

simon.vergauwen

09/13/2016, 6:59 PM

This won’t. I know that Mockito makes changes in

MOCKITO_CORE

and those changes normally only take affect before or after a test.

nstewart

09/14/2016, 12:07 AM

What are the steps to build Spek from the GitHub repo? I had to mess around with repositories to get here, but now I’m running

./gradlew build

and getting this stacktrace:

Copy code

INFO: Discovered TestEngines with IDs: [spek]
Exception in thread "main" java.lang.NoClassDefFoundError: org/jetbrains/spek/api/DescribeBody
> Buildiat org.jetbrains.spek.samples.AfterEachInDescribeTest$1.invoke(AfterEachInDescribeTest.kt:6)
	at org.jetbrains.spek.engine.SpekTestEngine.resolveSpec(SpekTestEngine.kt:108)
	at org.jetbrains.spek.engine.SpekTestEngine.resolveSpecs(SpekTestEngine.kt:50)
	at org.jetbrains.spek.engine.SpekTestEngine.discover(SpekTestEngine.kt:36)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:108)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:84)
	at org.junit.platform.console.tasks.ExecuteTestsTask.executeTests(ExecuteTestsTask.java:60)
	at org.junit.platform.console.tasks.ExecuteTestsTask.lambda$execute$0(ExecuteTestsTask.java:52)
	at org.junit.platform.console.tasks.CustomContextClassLoaderExecutor.invoke(CustomContextClassLoaderExecutor.java:33)
	at org.junit.platform.console.tasks.ExecuteTestsTask.execute(ExecuteTestsTask.java:52)
	at org.junit.platform.console.tasks.ConsoleTaskExecutor.executeTask(ConsoleTaskExecutor.java:38)
	at org.junit.platform.console.ConsoleLauncher.execute(ConsoleLauncher.java:54)
	at org.junit.platform.console.ConsoleLauncher.main(ConsoleLauncher.java:39)
Caused by: java.lang.ClassNotFoundException: org.jetbrains.spek.api.DescribeBody
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 13 more
:spek-samples:junitPlatformTest FAILED

raniejade

09/14/2016, 4:48 AM

@simon.vergauwen group blocks (describe, on, etc …) are evaluated eagerly during the discovery phase. While test blocks and fixtures (beforeEach, afterEach) are evaluated during the execution phase.

raniejade

09/14/2016, 4:51 AM

@nstewart http://jetbrains.github.io/spek/docs/latest/#setting-up.

simon.vergauwen

09/14/2016, 5:32 AM

@raniejade Ah, so in that second block of code. The

reset(mainView)

is executed in the discovery phase. And thus it doesn’t take effect.

simon.vergauwen

09/14/2016, 5:32 AM

Thanks 👍

nstewart

09/14/2016, 12:05 PM

@raniejade Sorry, I’m already using Spek in my project, getting the jar isn’t my issue. I’m trying to build Spek locally because iirc that is the only way to get

ConsoleRunner

so that I can run tests from the commandline (I’m unable to use Gradle currently).

raniejade

09/14/2016, 1:13 PM

@nstewart do you have the latest master? DescribeBody is a very old class.

nstewart

09/14/2016, 1:13 PM

I’m on commit

e71dc9f

, from 5 days ago

nstewart

09/14/2016, 3:08 PM

I was able to figure this out. I nuked the repo and tried again, and it worked. I don’t have experience with Gradle, but I guess it was using old build info? Thanks for the help @raniejade

john.shelley

09/14/2016, 6:17 PM

Is it a known issue that running a Spek in Android Studio doesn’t properly update the run panel tests name? ie: I named a context as

context(“My context A”)

and updated it to

context(“My context B”)

but it didn’t update in the Run panel.

adambl4

09/14/2016, 6:19 PM

have you added some Gradle

assemble

task to

Before launch

list?

adambl4

09/14/2016, 6:20 PM

For Android Studio, you need to add a Before launch gradle step to compile your test classes. If you have the default setup, adding assembleDebugUnitTest should suffice.

john.shelley

09/14/2016, 6:21 PM

is that in the docs? must be newly added, let me check

adambl4

09/14/2016, 6:21 PM

that is in the plugin docs https://github.com/raniejade/spek-idea-plugin

👍 1

john.shelley

09/14/2016, 6:28 PM

Dang that makes it take so much longer to run but it works. Any thoughts on why it takes so long and steps to fix it? would like to help out with the plugin if there is an attack plan

cedric

09/14/2016, 6:39 PM

@cedric has left the channel

john.shelley

09/14/2016, 6:44 PM

🤔 I added it to my Before Launch list but now the

context

block isn’t updating in Studio but the

it

block is.

adambl4

09/14/2016, 8:03 PM

@john.shelley the reason for this lies in that predicate https://android.googlesource.com/platform/tools/adt/idea/+/studio-master-dev/android/src/com/android/tools/idea/gradle/run/MakeBeforeRunTaskProvider.java#152

adambl4

09/14/2016, 8:06 PM

I have tried to rename the

SpekRunConfiguration

TestNGConfiguration

. It adds

Gradle-aware make

step to

before launch

list, but this step executes nothing

adambl4

09/14/2016, 8:06 PM

seems the only solution is to inherit

JUnitConfiguration