hello, how can I add kotlintest snapshot version as my dependency? I don't see how to do that in github page.

@Vinicius Araujo It would also be helpful to understand what you are trying to do.

Ah, I see. It's not a rest request to anywhere or anything like that?

when should one use shouldspec vs behaviourspec vs stringspec when unit testing? there’s so many different types its quite confusing

Hello, one question: is the kotlintest library multiplatform compatible?

Hi 🙂 I’m curious about the Arrow dependency that’s pulled in with KotlinTest — did you have a discussion somewhere about it being not part of the public API? For example having Arrow matchers in a separate artifact, and if KotlinTest uses Arrow internally then not exposing it? I’m not using Arrow but with KotlinTest I get tons of extension functions from it on most of the classes. Should I just e.g. exclude Arrow transitive dependency if I’m not gonna use those matchers? I only recall there was some discussion about splitting core and matchers into multiple artifacts but afaik the result was that there will be only one artifact. Maybe it’s something that could be reconsidered for the next major version?

Yeah, I'll give it a try anyways 👌

Feel free to ask us if you have any doubts 🙂

I’d like to vote for this feature, it’s I think the only that’s missing from classic bdd testing frameworks. Right now it’s a bit awkward to set isolation mode to per-test, and still have to write cleanup code after the last test. The advantage of current approach is we don’t need

lateinit

keyword, while setting stuff from closures will often make it necessary

Why this tests sometimes is success and sometimes failed?

fun loadData = MainScope().launch {
    view.showProgressDialog()
    // load data
}

Given(""){
    When(""){
        runBlocking {
            withContext(Dispatchers.Main) {
                presenter.loadData()
            }
        }

        Then("show progress dialog") {
            verify(exactly = 1) {
                view.showProgressDialog() 
            }
        }
    }
}

I am loading coroutines with this way

val mainThreadSurrogate = newSingleThreadContext("Main thread")
override fun isolationMode(): IsolationMode = IsolationMode.InstancePerLeaf

override fun beforeSpec(spec: Spec) {
    super.beforeSpec(spec)
    Dispatchers.setMain(mainThreadSurrogate)
}

override fun afterSpec(spec: Spec) {
    super.afterSpec(spec)
    mainThreadSurrogate.close()
}

i might have missed some announcement in this chat previously , apologies if this is the case, but is there any news about the gradle plugin which avoids the JUnit platform for kotlintest? Sam mentioned he was working on it some time ago, but i'm not sure what's the status of it currently.. Especially to handle nesting of tests

Hello,I followed this tutorial (https://www.zuhaibahmad.com/android-spec-testing/) but my output looks different than from the article. Mine looks like in attached pic - prints only “then” steps. But I wanna see all steps printed out. Can you suggest me a solution, please?

How come all the for-alls in

io.kotlintest.data

are

forall

instead of

forAll

like the capitalization pattern applied in the rest of the library? It took 5 minutes for me to realize that the compiler was giving problems because I was using, and importing, the wrong for-all.

Yep, ignores whitespace, etc. So

""" { "name" : "sam" }""".shouldMatchJson("      {            "name": \n\n: "sam" \n\n }"""

Tell me how to use

forall

with suspend functions?

Any idea how to debug failing test if all I see in console is

com.example.TestClass > com.example.TestClass > executionError FAILED
    org.mockito.exceptions.base.MockitoException at TestClass.kt:168
null
java.lang.NullPointerException
        at org.gradle.api.internal.tasks.testing.results.StateTrackingTestResultProcessor.started(StateTrackingTestResultProcessor.java:45)
        at org.gradle.api.internal.tasks.testing.results.AttachParentTestResultProcessor.started(AttachParentTestResultProcessor.java:38)

followed by a bunch of

Received a failure event for test with unknown id '4.74'. Registered test ids: '[4.70, 4.64, 4.1, :data:graphql-networking:test]'
java.lang.IllegalArgumentException: Received a failure event for test with unknown id '4.74'. Registered test ids: '[4.70, 4.64, 4.1, :data:graphql-networking:test]'
        at org.gradle.api.internal.tasks.testing.results.StateTrackingTestResultProcessor.failure(StateTrackingTestResultProcessor.java:103)
        at org.gradle.api.internal.tasks.testing.results.AttachParentTestResultProcessor.failure(AttachParentTestResultProcessor.java:43)

?

Hi everyone, I’m currently learning kotlintest by adding it to a spring boot project (which uses spring data jpa). A quick question around working with test data, I can load data into h2 as expected by including a

data.sql

file in my test resources folder, but I’d prefer to have fixtures per test, ideally using the

@Sql

annotation. However, this annotation doesn’t seem to be usable with the kotlintest spec style and applying it to a

beforeTest

method also doesn’t seem to work. Has anyone got any experience working with this sort of thing or any tips for a better way to work with test data? Thanks!

could you guys clarify the rerlationship between kotlintest and junit 5? is it that kotlintest is "built on top" of junit5, in a way? i'm trying to have an explanation ready for why i need to bring maven-surefire-plugin into an existing java project as we start adding kotlin/kotlintest

noticing some weird scoping of results: the following test class:``` class ScopeTest : ShouldSpec() { override fun isolationMode(): IsolationMode? = IsolationMode.InstancePerLeaf init { "scope1" { "scope2" { should("scope3") { } should("scope4") { } } } } ```

Hi, when using the generators for Property based testing, is there a way to genereate nulls for nullable types? e.g. we are calling

Gen.string()

I'm looking for something like

Gen.string().withNulls()

or similar

Hey everyone, just started learning about KotlinTest and tried using it on a small personal project, but as soon as I configured my CI on Bitrise and it ran my tests (which are written using BehaviorSpec) I noticed that the JUnit / Gradle test report outputs only the Then sentence as the test name (without the Given / When hierarchy to give context) which makes the Spec pretty much unusable for meaningful reports. Anyone facing this and found a workaround? (I found this StackOverFlow question, but no responses so far: https://stackoverflow.com/questions/56899882/kotlintest-junit-reports-arent-containing-the-behaviorspec-steps).

But something like

Gen.lines(file).take(1000)

would be very easy to use (and to implement)

👋 I have a small issue with running tests in Intellij IDEA; that when I double-click / mark and hit enter on a stringspec test in Intellij IDEA test results, the IDE does not lead me to the test code, instead, nothing happens. Has anyone experienced the same? A bit about the project if relevant: It's a Spring Boot 2.1.10 project with maven-surefire-plugin 3.0.0-M1, junit5 and kotlintest (tests are written in both junit5 and kotlintest). We also use testcontainers that have a dependency on junit4.

Anyone got example kotlintest being use in a ktor project?

Any idea why IntelliJ IDEA (2019.3) doesn't show

Run MyTest

for kotlintests in buildSrc? It works in the regular source tree, and the tests are run if I run

gradle test

on the command line.

is it frowned upon to add custom test context to a, say,

AbstractShouldSpec.ShouldScope

in order to make tests a bit cleaner? or is that the idea?

We want to do

a shouldMatchJson "foo"

How to attach listener/override listeners inside lambda based spec? https://github.com/kotlintest/kotlintest/blob/master/doc/reference.md#listeners usecase:

class MyTest: StringSpec({
    val destroyable = Destroyable()

    // attach afterSpec listener
    // override fun afterSpec() = destroyable.destroy()
})

Anybody have any good examples of using the StringSpec with listeners? First dip into kotlin in a while and I'm trying to start with unit testing.

is there a trick to getting jacoco to recognize kotlintest tests?

There's a ticket to fix that