I use the following configuration:

testImplementation "junit:junit:$junit_version"
testImplementation "org.jetbrains.kotlin:kotlin-test-junit:$kotlin_version"
testImplementation "org.jetbrains.spek:spek-api:$spek_version"
testImplementation "org.jetbrains.spek:spek-junit-platform-engine:$spek_version"
testImplementation "org.junit.platform:junit-platform-launcher:$junit_platform_version"

junitPlatform {
    filters {
        engines {
            include 'spek'
        }
    }
}

where

ext.kotlin_version = '1.1.3-2'
ext.junit_version = '4.12'
ext.junit_platform_version = '1.0.0-M4'
ext.spek_version = '1.1.2'

Please use triple back-ticks to quote code

😞

are there any plans to make spek a multiplatform utility?

i'm searching for a means of doing parameterized tests in a common module.

kotlin.test

is, at present, very simple and something more advanced like Spek is JVM-only

@jw yes, there are plans.

Hey guys, does Spek load all context functions at once?

Never mind, this has nothing to do with the fact of my tests being in a context function... The problem was related with a mock.

Depends on what you mean by “load”, basically any “group” function (like

context

,

describe

,

given

) will go though full cycle of group initialization (like

beforeGroup

,

beforeEachTest

,

memoized

with proper cache level)

my spek output is really hard to parse for big object comparisons

any way to get something more readable?

like diffs for lists and such would be nice

hmm, but how is Spek related to that? It doesn’t provide assertions, users usually prefer AssertJ for that its human-oriented exception messages and fluent builder-like syntax

yeah i think you're right after thinking it over

i need a better assertion library

There are few Kotlin oriented: -

<https://github.com/winterbe/expekt>

-

<https://github.com/MarkusAmshove/Kluent>

-

<https://github.com/evant/assertk>

But AssertJ works well too

i was using kluent, but it essentially just mapped to junit so the error messages were ehhhh

assertk looks good!

there’s also Hamkrest https://github.com/npryce/hamkrest

@liamd huh, didn’t know that, thanks for sharing! I still don’t see many reasons to migrate from AsserJ 🙂

Hey guys, I'm trying to run all my Spek tests trough the terminal but when I execute the command

gradle clean build

or

gradle test

I always get the following output:

> Task :junitPlatformTest

Test run finished after 89 ms
[         1 containers found      ]
[         0 containers skipped    ]
[         1 containers started    ]
[         0 containers aborted    ]
[         1 containers successful ]
[         0 containers failed     ]
[         0 tests found           ]
[         0 tests skipped         ]
[         0 tests started         ]
[         0 tests aborted         ]
[         0 tests successful      ]
[         0 tests failed          ]

Does anyone know why this is happening?

Did you properly setup JUnit5 Gradle integration?

junitPlatform {
    platformVersion '1.0.0-M4'

    filters {
        engines {
            include 'spek'
        }
    }
}

Yes, but is still not working

Do you have other JUnit5 engines?

No

This is my build.gradle file:

// Plugin settings
buildscript {
    repositories { mavenCentral() }
    dependencies { classpath "org.junit.platform:junit-platform-gradle-plugin:1.0.0-M4" }
}

plugins {
    id 'application'
    id 'com.heroku.sdk.heroku-gradle' version '0.2.0'
    id 'org.jetbrains.kotlin.jvm' version '1.1.4'
}

apply plugin: 'org.junit.platform.gradle.plugin'

junitPlatform {
    filters {
        engines {
            include 'spek'
        }
    }
}

// Project settings
group 'project-name'
version '1.2'
mainClassName = "config/api/Application"

sourceSets {
    main.java.srcDirs += 'src/main/kotlin/'
    test.java.srcDirs += 'src/test/kotlin/'
}

// Dependency settings
repositories {
    jcenter()
    maven { url "<http://dl.bintray.com/jetbrains/spek>" }
}

def kotlin_version = '1.1.4'
def spek_version = '1.1.2'

dependencies {
    testCompile "org.jetbrains.spek:spek-api:$spek_version"
    testRuntime "org.jetbrains.spek:spek-junit-platform-engine:$spek_version"
    testRuntime 'org.junit.platform:junit-platform-launcher:1.0.0-M4'
    testCompile 'com.nhaarman:mockito-kotlin:1.5.0'
    testCompile 'org.amshove.kluent:kluent:1.26'
    testCompile 'com.github.javafaker:javafaker:0.13'

    compile "org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"
    compile "org.jetbrains.kotlin:kotlin-reflect:$kotlin_version"
    compile 'com.github.salomonbrys.kodein:kodein:4.1.0'

    compile 'com.sparkjava:spark-core:2.6.0'
    compile 'com.fasterxml.jackson.core:jackson-databind:2.8.6'
    compile 'org.slf4j:slf4j-simple:1.7.21'
    compile 'org.mongodb.morphia:morphia:1.3.2'
    compile 'io.github.lukehutch:fast-classpath-scanner:2.4.2'
}

Apparently there isn't anything wrong but I'm still unable to run the tests through the terminal

Anyone else having issues with the spek plugin and creating new Spek configurations in Android Studio 3.0.0-beta2?

explain what problem do you have

It doesn’t let me create a configuration and shows no error. I downgraded to 0.4.2 but experience the same issue. Feels like an issue with beta

Hey guys