kotlinlang #spek

object SplashScreenPresenterTest: Spek({
    describe("SplashScreen presenter") {

        lateinit var viewMock: SplashScreenView

        describe("on no migration running") {

            val loadApplicationStateMock = mock<LoadApplicationState> {
                onBlocking { invoke(any()) } doReturn ApplicationState.MIGRATION_CLASSIC
            }
            val splashScreenPresenter = SplashScreenPresenter(viewMock, loadApplicationStateMock)
            it("should route to standard welcome screen") {
                runBlocking {
                    splashScreenPresenter.loadState()
                    verify(viewMock, times(1)).moveToClassicMigrationScreen()
                }
            }
        }
}

I want to use viewMock in multiple describe. I use verify, so I need to reset the mock for each describe. How can I init my viewMock for each describe?

2 replies · 2 participants

dzaitsev

01/11/2019, 9:40 AM

Hey. I’ve been using Spek for a year and pretty happy with it. Recently we started migration to Spek 2 and faced several issues. 1. ⚠️ Our tests are green if we run them from Android Studio, but ≈80% of them become red if we run tests from Gradle. We get lots of `java.lang.VerifyError`s. Therefore we can’t gather jaCoCo coverage. 2. To be able to run tests from IDE we have to annotate speks with

@RunWith(JUnitPlatform::class)

but it requires us to change kotlin dependency from

kotlin-stdlib-jdk7

kotlin-stdlib-jdk8

because it needs streams. Any advice? spek 2.0.0-rc.1, kotlin 1.3.11, AS 3.4 Canary 10, Gradle 5.1

11 replies · 2 participants

snowe

01/15/2019, 12:38 AM

I've spent 30 minutes on it and haven't gotten anywhere.

17 replies · 2 participants

mmaillot

01/16/2019, 9:25 AM

The plugin seems not compatible with the new version of Android Studio (3.3). The green arrow to launch tests is showed but when I click on it, I have the

Nothing here

message. I can run my test with gradle.

13 replies · 2 participants

mmaillot

01/18/2019, 1:18 PM

Is it possible to run all tests from Android Studio? If I right click on test folder then click on

Run 'Spek tests in....'

, I got an error:

Test framework quit unexpectedly

without more information

4 replies · 2 participants

charleskorn

01/20/2019, 10:10 PM

Are there any plans for Spek to support Kotlin/Native?

1 reply · 2 participants

01/29/2019, 9:55 AM

hi there want to understand state of spek and related staff can anyone share blogpost or tweets about any release plans etc. tnx!

4 replies · 3 participants

snowe

01/29/2019, 4:28 PM

or even compose better functionality instead of inherit.. It seems hard with the way that it's all run in a block.

10 replies · 3 participants

snowe

01/31/2019, 1:50 AM

Spek fails to run in gradle, but succeeds in intellij. any thoughts?

-.txt

13 replies · 3 participants

snowe

02/01/2019, 5:44 AM

has anyone had any success running

pitest

with spek? I get

10:42:19 PM PIT >> INFO : Sending 86 test classes to minion
10:42:19 PM PIT >> INFO : Sent tests to minion
10:42:20 PM PIT >> INFO : MINION : 10:42:20 PM PIT >> INFO : Checking environment
10:42:20 PM PIT >> INFO : MINION : 10:42:20 PM PIT >> INFO : Found  0 tests
10:42:20 PM PIT >> INFO : MINION : 10:42:20 PM PIT >> INFO : Dependency analysis reduced number of potential tests by 0
10:42:20 PM PIT >> INFO : MINION : 10:42:20 PM PIT >> INFO : 0 tests received

2 replies · 2 participants

tapchicoma

02/01/2019, 1:13 PM

is it possible to run Spek test n-times?

4 replies · 2 participants

raniejade

02/04/2019, 7:00 AM

Hey all! After a long and very slow development, I'm happy to announce that Spek 2 is out. Highlights of the changes can be found here: https://github.com/spekframework/spek/releases/tag/2.0.0.

😍 1

🎉 19

👍 1

1 reply · 2 participants

Nikky

02/06/2019, 4:56 AM

i updated to 2.0.0 and i got this:

https://i.imgur.com/SkeXjL8.png▾

Feb 06, 2019 5:52:02 PM org.junit.platform.launcher.core.DefaultLauncher handleThrowable
WARNING: TestEngine with ID 'spek2' failed to discover tests
java.lang.IllegalStateException: it.javaClass.`package` must not be null
	at org.spekframework.spek2.junit.SpekTestEngine.discover(SpekTestEngine.kt:51)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:168)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:155)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:128)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:102)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:82)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor.stop(JUnitPlatformTestClassProcessor.java:78)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:61)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.stop(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:132)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:175)
	at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:157)
	at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)

or maybe its not really related.. but the error seems to make no sense

3 replies · 2 participants

alilosoft

02/09/2019, 5:07 AM

Hi, are there any plans to continue spring support extension

1 reply · 2 participants

alilosoft

02/10/2019, 9:47 PM

Hi, I was playing with Spek the last two days, and I run into some problems, and I'm confused. The first problem is related to running tests: I wrote some Speks and JUnit tests just as a demo, when I run the tests with IntelliJ everything was ok!, but when I try to run the tests with Gradle then only the Speks are discovered but JUnit tests are not 😭 When I remove

includeEngines("spek2")

from my gradle build then all the tests run fine 👍 So my question: Is this behavior intended or is it a bug? My second problem is related to MockK:

7 replies · 3 participants

alilosoft

02/10/2019, 10:06 PM

@raniejade Thanks for the clarification I have another issue with MockK, I tried to write a sample test using MockK and Spek and the test run correctly with gradle test, but when I try to run the test with Spek plugin in IntelliJ I get an exception, and I'm not sure if the problem is in MockK or in Spek plugin???

3 replies · 2 participants

alilosoft

02/10/2019, 10:32 PM

@raniejade Sorry, but I have another concern 🤔 Is it possible to write [TestFX](https://github.com/TestFX/TestFX) tests with Spek?

6 replies · 2 participants

christophsturm

02/13/2019, 12:44 PM

pitest has a plugin for junit5 so that should just work

10 replies · 3 participants

rook

02/15/2019, 7:08 PM

NoClassDefFoundError

It looks like I’m missing a dependency or something?

39 replies · 2 participants

tapchicoma

02/18/2019, 9:54 AM

Is it a lot of work to also publish plugin to canary versions of Android Studio? Would be nice to have versions to canary builds as well.

2 replies · 2 participants

Slackbot

02/21/2019, 8:28 PM

This message was deleted.

2 replies · 3 participants

pavel

02/21/2019, 8:57 PM

Is there a way to get it by

Scenario

instead?

3 replies · 3 participants

Shan

02/23/2019, 11:52 PM

https://stackoverflow.com/questions/54847416/warning-testengine-with-id-spek2-failed-to-discover-tests-with-gradle-v5-2-1 posted on Stack as well if anyone wants to answer there instead 👍

10 replies · 2 participants

Shan

03/05/2019, 7:19 AM

Is there a Spek equivalent of KotlinTest's "eventually" method? https://github.com/kotlintest/kotlintest/blob/master/doc/nondeterministic.md

1 reply · 2 participants

raniejade

03/23/2019, 1:54 AM

Quick poll. Do you depend on the laziness of

memoized

on your tests? https://github.com/spekframework/spek/pull/660 came up to eagerly evaluate

memoized

during the execution phase instead of evaluating on access. Options: :yes:, 🇳🇴 and 🙃 if you didn’t know that

memoized

is lazy.

🙃 4

🇳🇴 3

4 replies · 3 participants

svenjacobs

03/28/2019, 2:02 PM

Hi all, is there a way in Spek 2.0 to run some test initialization code once before all tests (of all groups) are run? So something like

beforeGroup

but with a greater scope?

12 replies · 2 participants

Title

svenjacobs

03/28/2019, 2:02 PM

Hi all, is there a way in Spek 2.0 to run some test initialization code once before all tests (of all groups) are run? So something like

beforeGroup

but with a greater scope?

raniejade

03/28/2019, 11:32 PM

Can you post a snippet on what you are trying to achieve?

svenjacobs

03/29/2019, 10:53 AM

Please see here https://github.com/rewe-digital/katana/blob/master/core/src/test/kotlin/org/rewedigital/katana/InjectionTests.kt#L18 This works however I would like to execute this line once before all tests from all groups are run.

raniejade

04/02/2019, 8:26 AM

@svenjacobs your doing the correct way, you can move the

beforeGroup

inside

desribe("Injection")

which will be only executed for that group.

svenjacobs

04/02/2019, 8:41 AM

@raniejade However as I said earlier 😉 I want this code to be run only once before all groups. Not just this test group, but all other test groups, too.

https://github.com/rewe-digital/katana/tree/master/core/src/test/kotlin/org/rewedigital/katana

raniejade

04/02/2019, 9:28 PM

then having on the root scope is fine. You get an extra execution for the root scope, is that ok?

svenjacobs

04/03/2019, 7:11 AM

How do I declare a root scope? Can you please show an example?

raniejade

04/03/2019, 9:29 PM

you’re already doing it 🙂 declaring a

beforeGroup

just before the first describe. Just realised that I have a typo in my previous reply 😂

then having on the root scope is fine -> then having one on the root scope is fine

svenjacobs

04/04/2019, 9:49 AM

But how can I assure that the test group with

beforeGroup

is run as the first test when I run

./gradlew test

? Are they called in alphabetical order? So will

A_Test.kt

run before

B_Test.kt

? And what if an order is not guaranteed?

raniejade

04/04/2019, 11:20 AM

beforeGroup

is not global and won’t affect other classes.

class A: Spek({
  beforeGroup { ... }
})

class B: Spek({
  beforeGroup { ... }
})

beforeGroup

and

are isolated.

svenjacobs

04/04/2019, 11:27 AM

I know but I need a global solution

raniejade

04/04/2019, 9:34 PM

there’s no global solution. You can create an extension then just invoke it on all of your tests.

View count: 1