kotlinlang #spek

@raniejade I'm having trouble understanding memoized cache modes, its not in the docs and the code is very nice, but I still don't have enough of a global picture to understand...

raniejade

10/16/2017, 8:06 AM

by default it caches per test (

it

and

on

)

raniejade

10/16/2017, 8:08 AM

you can pass in

CachingMode.GROUP

to do it per group (

given

describe

, etc …)

raniejade

10/16/2017, 8:09 AM

CachingMode.SCOPE

will effectively make it a singleton

dave08

10/16/2017, 8:18 AM

@raniejade Why do you save the value in a stack for GROUP beforeEachGroup?

mkporwit

10/16/2017, 8:21 AM

OK, so one more question... I'm trying to replicate the following code/behavior in Spek:

Copy code

class ProfileTests {
    companion object {
        val userProfileRedisContainer = KGenericContainer("redis:latest").withExposedPorts(6379)!!

        @BeforeClass
        @JvmStatic
        fun classSetup() {
            userProfileRedisContainer.start()
        }

        @AfterClass
        @JvmStatic
        fun classShutdown() {
            userProfileRedisContainer.stop()
        }
    }

    private val userProfileRedis = makeRedisHandler(userProfileRedisContainer.containerIpAddress, userProfileRedisContainer.getMappedPort(6379))

mkporwit

10/16/2017, 8:21 AM

In my Spek implementation, I have:

Copy code

object ProfileHandlerSpecHelper {
    val userProfileRedisContainer = KGenericContainer("redis:latest").withExposedPorts(6379)!!
}

class ProfileHandlerSpec: Spek({
    beforeGroup {
        ProfileHandlerSpecHelper.userProfileRedisContainer.start()
    }

    describe("a profile handler") {
        val userProfileRedis = makeRedisHandler(ProfileHandlerSpecHelper.userProfileRedisContainer.containerIpAddress, ProfileHandlerSpecHelper.userProfileRedisContainer.getMappedPort(6379))

mkporwit

10/17/2017, 5:57 PM

Has anyone gotten JaCoCo test coverage analysis working with Spek? I had working JaCoCo coverage for my old JUnit4-based tests, but I don't get them on the new Spek ones. I've got the following relevant config in my build.gradle:```apply plugin: 'jacoco' apply plugin: 'org.junit.platform.gradle.plugin' jacoco { toolVersion = "0.7.9" reportsDir = file("${buildDir}/reports/jacoco") } jacocoTestReport { reports { xml.enabled true csv.enabled false html.destination file("${buildDir}/reports/jacoco/html") } } junitPlatform { filters { engines { include 'spek', 'junit-jupiter', 'junit-vintage' } } enableStandardTestTask true } ``` Is there anything else I should be tweaking? The project now only has Spek-based tests.

artem_zin

10/17/2017, 6:04 PM

Most likely jacoco Gradle plugin hooks only to regular JUnit4/TestNG test execution path

mkporwit

10/17/2017, 6:05 PM

Ah. That, as they say, would be unfortunate.

artem_zin

10/17/2017, 6:05 PM

You might need to manually hook it to junitPlatform Gradle plugin, similar to this https://github.com/pushtorefresh/storio/blob/56e678a15e137239b00270d99346dddd0a93de33/gradle/jacoco-android.gradle

mkporwit

10/17/2017, 6:05 PM

Spek uses JUnit5 under the covers, yes?

artem_zin

10/17/2017, 6:05 PM

correct

artem_zin

10/17/2017, 6:06 PM

I believe this should already be discussed somewhere in Jacoco/Gradle issue trackers, JUnit5 is getting more and more attention after 1.0 release

artem_zin

10/17/2017, 6:07 PM

Here you go https://github.com/junit-team/junit5/issues/1024

mkporwit

10/17/2017, 6:07 PM

Yeah, OK. This seems relevant as well: https://stackoverflow.com/questions/39362955/gradle-jacoco-and-junit5

mkporwit

10/17/2017, 6:07 PM

Gives me something to chase down.

artem_zin

10/17/2017, 6:07 PM

yep yep, also saw that, but GitHub issue has more details