Don’t get me wrong. I have bunch of tests written in Kotlintest and would love to stay with it. First of all, I prefer

init{}

syntax way more than lambda in constructor. AFAIR spek doesn’t have support for

init{}

. So if you guys can fix this

executionError

in kotlin test runner I will be more than happy 😉

We can fix and release as part of 3.3.2

perfect. Any ETA of this

3.3.2

release?

Tomorrow night I think.

Sounds great! 🙂

Thank you. Really appreciate it.

You're welcome.

I've made that change on release/3.3 branch

I'll let @LeoColman do a release once he's happy with it

I'm on it!

@sam I think we already had a 3.3.2 tag

But it was never published, so I'll recreate 3.3.2

KotlinTest 3.3.2 was just released. https://github.com/kotlintest/kotlintest/releases/tag/3.3.2

It will be soon available in Maven Central

I'll edit the changelog later

Did you release from master or the release/3.3 branch

The release/3.3 branch has been deleted? @LeoColman

I thought you had maybe released from master, but it looks like the release is good, you just deleted the branch after. I'll remake it, because that release branch is meant in case we need to do further bug fixes on 3.3.x

Do you plan to update the version of

kotlintest-extensions-system

in accordance with the latest versions of kotlintest? Now they are version 3.2.1, while the rest of the builds are already available version 3.3.2

They moved into kotlintest-extensions I think

Perfect. Thank you guys for the

3.3.2

release. I confirm that

executionError

is no longer reported. Great work!

Awesome

@sam sorry for deleting it. Didn't know you'd need it. I have it local if you couldn't restore

I already restored but cheers

Hej @sam and @LeoColman, regarding

executionError

which is fixed in

3.3.2

I’d like to ask about

initializationError

, reported by Gradle in some specific scenario. Consider following example:

class InitErrorTest : ExpectSpec() {

  init{
    context("This context") {
      throw RuntimeException("should fail")
    }
  }
}

Running this spec within IntelliJ shows that context fails with “Should fail” message. However on Gradle it looks like this:

mypackage.InitErrorTest > mypackage.InitErrorTest > initializationError FAILED
    java.lang.RuntimeException at InitErrorTest.kt:10

Is it something on the kotlintest side as well and can be fixed or am I using

context { }

in a wrong way and should nest

expect { }

inside? When nesting though:

init{
    context("This context") {
      expect("failure"){
        throw RuntimeException("should fail")
      }
    }
  }

Gradle doesn’t show exception message:

mypackage.InitErrorTest > Expect: failure FAILED
    java.lang.RuntimeException at InitErrorTest.kt:11

1 test completed, 1 failed

, however IntelliJ does. Thanks in advance for any hints.

So the

context { expect { } }

way is how it should be done

What's the error you are seeing, that the full stack trace isn't printed by gradle ?

Gradle won't print the full stacktrace unless you tell it to do it

In my projects I configure it this way:

testLogging {
        events "PASSED", "FAILED", "SKIPPED", "STANDARD_ERROR", "STANDARD_OUT"
        showStackTraces = true
        exceptionFormat = 'full'
    }