@yigit: fixed. But hopefully init will go soon

thanks! btw i really love its design so 👍👍 on that!

Thanks simple smile

@hhariri: Any feedback on https://github.com/JetBrains/spek/pull/48 ? I think it's a great idea, easier to read and to understand, especially for non-kotlin developers.

That’s one of the options. The thing is if we switch, I think it should be for a vNext and also make sure that we don’t switch again (at least for some long time). And I’ve not had a chance to try out everything with that approach. What do others think?

You could allow both syntax by providing two constructors, that way it would not break previous code.

Btw, what are the other options you are thinking of ?

(Sorry, the pull-request uses optional parameter, so with this PR, both syntaxes are already available)

@salomonbrys: current style has some serious shortcomings and it’s primarily due to the way the tests are constructed using the constructor. I’d rather get rid of it. The above approach is pretty much the same, as it’s still delegating it to constructor.

To work around these shortcomings, we’d have to pretty much drop JUnit dependency. If we do that, we lose a bunch of out of the box functionality such as IntelliJ IDEA integration and build tools integration.

Hey guys, what are you using for test doubles with spek2?

Hello, I just started using Spek framework on Android Studio, but I'm noticing that the inner highlighting of the describe functions and general IDE syntax highlighting stops working beyond the first describe function, is anyone experiencing the same? Here is a screenshot to describe what I mean

Anyone is facing an issue, where instant error highlighting stops working while typing Spek tests? I have to run the test first to get the compile error under the Build Output panel before Android Studio starts highlighting the error.

@raniejade I'm wondering, any ETA for this PR to be released? It would be nice to have suspend lambdas, rather than keep doing

runBlocking { assertion }

https://github.com/spekframework/spek/pull/835

Hi, does anyone have a working example of a test using Mockk’s

mockkStatic

? I can’t make it work with Spek. In JUnit

mockkStatic

works fine.

I’m currently migrating from spek1 to spek2:

<dependency>
      <groupId>org.spekframework.spek2</groupId>
      <artifactId>spek-dsl-jvm</artifactId>
      <version>${spek.version}</version>
      <scope>test</scope>
      <type>pom</type>
    </dependency>
    <!-- <https://mvnrepository.com/artifact/org.spekframework.spek2/spek-runner-junit5> -->
    <dependency>
      <groupId>org.spekframework.spek2</groupId>
      <artifactId>spek-runner-junit5</artifactId>
      <version>${spek.version}</version>
      <scope>test</scope>
    </dependency>

This results in none of my tests being run, as they aren’t found. What’s going on?

Hello there, Since spek is now multiplatform, when will it run js tests?

I noticed this issue related to the IJ version and spec version compatibility on looking through past issues. Still seeing it however after keeping both the IJ and spek version to 2.0.11 java.lang.NoSuchMethodError: org.spekframework.spek2.runtime.execution.DiscoveryRequest.<init>(Lorg/spekframework/spek2/runtime/discovery/DiscoveryContext;Ljava/util/List;)V at org.spekframework.ide.Spek2ConsoleLauncher.run(console.kt:20) at org.spekframework.ide.ConsoleKt$main$1.invoke(console.kt:45) at org.spekframework.ide.ConsoleKt$main$1.invoke(console.kt) at shadow.com.xenomachina.argparser.SystemExitExceptionKt.mainBody(SystemExitException.kt:74) at shadow.com.xenomachina.argparser.SystemExitExceptionKt.mainBody$default(SystemExitException.kt:72) at org.spekframework.ide.ConsoleKt.main(console.kt:43)

Hello, I would like to switch to IDEA 2020.2 EAP, but I need Spek plugin to run tests. Could somebody tell me, please, how to build the plugin locally with support for IDEA 2020.2?

Maybe this information would be useful for the Spek developers. @robstoll was able to reproduce the error: “Seems like spek is a using the wrong classpath and is not resolving all transitive runtimeOnly dependencies (maybe this is a bug of Android Studio)”

am I doing something wrong or is it normal that 100 lines long spec (1x

describe

and 5x

it

) takes awfully long for syntax highlighting to kick in? anywhere between 10-20s is it even related to spek or is it kotlin compiler issue? I've tried searching this channel for solutions but haven't found anything

Is this still the standard way to run suspending functions in Spek test? (Using

runBlocking

)

Then("event store should be empty") {
        runBlocking {
          // findAll is a suspending function
          eventStore.findAll().shouldBeRight { it.shouldBeEmpty() }
        }
      }

Its not the biggest deal, although it does make some tests a bit more verbose. I see some talk about this in the channel history but wasn’t sure if this was still the cleanest way to do it

What would be a better practice with Spek?

object MyTestCase : Spek({})

vs

class MyTestCase : Spek({})

Hi, any plans to release a new plugin version supporting IDEA 2020.3?

Hey folks! Due to my interests shifting and a burning drive to do something else - I've decided to step down as maintainer and start looking for new ones: https://github.com/spekframework/spek/issues/959 - if you know anyone that is interested please let me know. I'll be sticking for a while until a new maintainer (or more) is found.

(multiplatform question) Can I run spek on

commonTest

? or should I create tests only on android/jvm test folders?

When is the Spek plugin for intellij 2021.2 released?

@gammax looks like you are the moderator of this channel. Do you also coordinate development?

Does anyone have experience combining spek with koin? They seem incompatible.

Hey folks, is there any way to group tests and run those groups separately from the command line? Like Junit's

@Tag("integration")

annotation and then run

./gradlew test -DexcludeTags="integration"

to run only all other tests.