You can follow progress here https://github.com/spekframework/spek/issues/331

It’s time for me to write some docs, I guess 🙂 Personally I voted to remove

Action

at all, because most of the time all you need is

Group

. Also, it scales well with situations when suddenly your

Action

is needed to be nested. I. e. you what should be done after click and suddenly there is another click or something.

Sure you guys know this but if you get the order wrong the tests still run but none get executed. At some point it would make sense for it to detect the syntax being wrong, no?

@codeslubber can you give an example? Not sure what do you mean by wrong order

if it's expecting say given/on/it and you do on/given/it, it doesn't spit up a syntax error but..

I had not been using Spek for a while cause it was not working in android, it's nice to have it back..

ah I see, @codeslubber we've discussed it right before your message ^ and I've posted a link to follow progress 🙂

set the channel topic: A specification framework for Kotlin: https://github.com/JetBrains/spek

Btw, here is a talk about Spek 2.x (with QA at the end) that might answer some of your questions (not yours, Rob haha)

yep, I actually was comparing it to JUnit5, they support it natively now, but in "junit" way which is reflection/annotation based instead of just api that you code against rather than defining metadata for JUnit to discover it

yeah. Makes sense. annotations do add some extra flexibility to do some setup stuff but are far more complex. I remember wasting so much time writing rules in junit 4. I started writing my own specification engine (cloned from someone else's) but found spek on the way - https://github.com/bangarharshit/Oleaster

haha, welcome to the club 🍾

Not really a Spek specific question, but my API heavily depends on an external API to proceed with execution of the code base. Should I be making these API calls in my tests, or should I mock my responses, a fairly extensive and exhaustive exercise?

@artem_zin @harshitbangar We also started to write our own specification engine. At the first glance it looks very similar to spek, but it has much less boiler-plate code and also favours independent tests scenarios by default. - https://github.com/elpassion/MiniSpek

@kasper.kondzielski looks interesting. spek is much more than just a runner/test engine(this is basically what I wrote in the first iteration). It has a discovery engine of its own, well defined lifecycle. It is really extensible and support a lot of cases such as custom class loader. In my framework I just hacked all this. Figuring out all this needs substantial effort and was a duplication. The biggest downside of spek is that there is no runtime representation (junit has java.lang.reflect.method) and the speks in the same class uses the same instance. Tests are not isolated but there are workarounds such as memoized or proper cleanup/setup.

Spek needs to stay away from reflection, support is not consistent across platforms (jvm, js, native).

Good point.

are there any nightly/preview release? i want to use spek 2.x release in robolectric

hi, I'm using the Spek idea plugin, and I'm trying to run multiple Spek objects at once

it will not let me populate the "package" field when I select the package type rather than spec

known issue?

@tmseiler this works for me if I right-click the test folder, or a package and select “run all tests”

when I do that, it creates a temporary JUnit run configuration, rather than a Spek run configuration

is that your experience too? I'm not sure how to get the JUnit one working with idea

Yeah it creates a junit run configuration for me too, but running it executes all the spek tests

I do have the junit-platform-runner specified in my gradle dependencies - maybe that’s the difference?

There should be a Run all specs in <package> when right clicking a package or directory. Run all tests is managed by junit plugin not spek.

all right, the JUnit approach worked when I added the runner to the "testCompile" directive rather than just the testRuntime one (I'm still new to gradle)

Hi, i am trying out spek and so far i realy like it. But I just can not find anything regarding how to start speks with gradlw from command line (for CI server). Is it possible?

Sure, if you use JUnit 5 Gradle Plugin try

./gradlew :your-module:tasks

to figure out correct task