@jackmiras it worked completely for me. In terminal and intellij, with only a single Spek test in my whole project though (we have 160k lines of code and about 1700 tests total)

Are you using Maven or Gradle?

@jackmiras maven.

@snowe I'm using gradle in here... I've tried to refresh all the dependencies but I'm still unable to run a single test file in the IntelliJ IDEA.

When I run the tests using the terminal, everything works fine but when I try to run the tests in the IntelliJ nothing works.

You probably need to include the engine and platform declarations

@jackmiras http://junit.org/junit5/docs/current/user-guide/#running-tests-ide-intellij-idea

I thought that this was already included by the

testRuntime "org.jetbrains.spek:spek-junit-platform-engine:$spek_version"

that is specified at Spek documentation.

But I will try add those JUnit engine dependencies, if things start work properly again I will inform you guys

Hey @snowe you where right! There was some libraries missing but was not the engine itself... The

testRuntime "org.jetbrains.spek:spek-junit-platform-engine:$spek_version"

is the Spek implementation of the JUnit engine, but in order to be able to run tests on IntelliJ IDEA I have to have

testRuntime 'org.junit.platform:junit-platform-launcher:1.0.1'

as dependency as well.

Anyway thanks for helping me!!

awesome yeah the launcher I thought was specified in the doc to include by default so I didn't mention it. I didn't reread the link to remember what it said lol. Glad I could help

How are you supposed to use the spek extensions?

Not sure, but I'll download it today.

hmm, it’s quite easy to miss that you accidentally nested

it

blocks. The inner blocks are just never executed and you erroneously think that all tests have succeeded. The DSL should prevent nesting

it

blocks 🙂

FYI, on spekframework.org the example test is called

SimpleTest

and on http://spekframework.org/docs/latest/#_basic_structure it’s called

SimpleSpec

. What’s the recommended naming?

We usually go with

*Spec

, but I think it is a matter of personal preference.

Okay, thanks. But at least the website should be consistent imo 🙂

Good point, we'll fix that, thanks 🙂

We found that for compatibility with running tests in IntelliJ we had to name them *Test. (May not still be an issue)

I use *Spec and they are running ok in Intellij

yep, that shouldn’t matter for tooling

does spek work with spring now? (

@Autowired

and such)?

I suppose with JUnit it works through Rule or Runner?

can the spek DSL access instance fields though?

what do you mean by that? 🙂

@artem_zin were you responding positively to my question?

In the past I had issues because you couldn't use annotations in the

Spek

constructor

Well, in order to autowire fields into the spek they’d need to be instance-level fields but the tests in Spek are part of a DSL closure passed to the (superclass) constructor so I don’t believe they’d be able to access those fields. Maybe I’m missing something.

@snowe I was asking how it’s currently done with JUnit 🙂 Theoretically, you should be able to use everything you used with JUnit support for Spring