kotlinlang #spek

@raniejade My mac crashed and wiped out the stack traces... next time it happens I'll attach the source code and you can take a look. Happened 11 times yesterday, so it should be a pretty easy repro.

mkporwit

11/09/2017, 12:11 AM

What's the mechanism for printing out the spek results in a gradle build target?

mkporwit

11/09/2017, 12:11 AM

I'm getting nice Spek output when I run the tests in IntelliJ, and I can fully expand it and read them like a specification.

mkporwit

11/09/2017, 12:12 AM

If I wanted to emit a fully expanded Spek output when I run from the command line, how could I do that?

mkporwit

11/09/2017, 12:12 AM

I'm running under JUnit5

raniejade

11/09/2017, 12:19 AM

@mkporwit maybe try including

org.junit.platform:junit-platform-console

raniejade

11/09/2017, 12:20 AM

ahh nvm, it doesn't include

META-INF/services

file.

raniejade

11/09/2017, 12:25 AM

Copy code

import org.junit.platform.console.options.Details
junitPlatform {
    ...

    details = Details.TREE // FLAT, VERBOSE
}

👍 1

mkporwit

11/09/2017, 12:29 AM

@raniejade is this for the plugin crash or for for my question about test output?

raniejade

11/09/2017, 12:29 AM

test output

raniejade

11/09/2017, 12:29 AM

🙂

mkporwit

11/09/2017, 12:30 AM

👍

reline

11/13/2017, 9:02 PM

How far does Spek support nesting of groups? for example, this code is two nested groups, but I'd like to do around three or four

Copy code

given("some context") {
        on("executing some action") {
            it("should pass") {
                assertEquals(2, 2)
            }
        }
    }

sngrekov

11/13/2017, 9:07 PM

We have around 10-15 nested groups and it's fine

reline

11/13/2017, 10:43 PM

Ah, the problem was that I had another group inside of an

on

group

Copy code

on("executing some action") {
   given("this doesn't work") {
       it("will break") {
          ...
       }
    }
}

reline

11/13/2017, 10:43 PM

thanks for letting me know it works 👍

artem_zin

11/14/2017, 1:19 AM

on is not a

group

, it's an

action

, so you better not nest anything in it, unfortunately we can't prevent compiler from allowing you to do that 😞

✅ 1

robfletcher

11/14/2017, 4:52 PM

Weirdly it seems to work as well

robfletcher

11/14/2017, 4:53 PM

I usually write my speks with a

Copy code

describe {
  on {}
  it {}
  it {}…
}

but I’m never quite sure if that’s “right”

robfletcher

11/14/2017, 4:54 PM

I’ve noticed it’s the biggest source of confusion for team members new to Spek

artem_zin

11/14/2017, 9:23 PM

so, we have two styles of writing tests, I personally and hopefully @artur.dryomov and Juno teams recommend to not use

on

(

action

) unless you have really good reasons to

artem_zin

11/14/2017, 9:24 PM

action

basically shares state between `test`s inside the

action

artem_zin

11/14/2017, 9:24 PM

I'd recommend to use

group

(`context`/`describe`/`given`) because they execute each

test

(

it

) separately

artem_zin

11/14/2017, 9:25 PM

So, something like https://github.com/spekframework/spek/blob/b7fbb9d60aa692b911b2e15d7d1db70e677e7e21/samples/src/test/kotlin/org/spekframework/spek2/samples/MemoizedSpec.kt

robfletcher

11/14/2017, 10:04 PM

Yeah, typically I do it that way because I want the action to execute once and then to make multiple assertions about what happened.

11/14/2017, 11:30 PM

Did you consider a runtime error with a descriptive message if there are nested

on

orangy

11/14/2017, 11:36 PM

May be using @DslMarker would help to avoid builder errors? (if I understood it right)

artem_zin

11/14/2017, 11:45 PM

Good point @orangy! gonna investigate that option, @jk I think we've discussed that back in Spek 1.x times, 2.x should have enough runtime info to raise runtime exception I think

11/14/2017, 11:46 PM

If you can use DslMarker that will be the best choice 😀