Hello, I have an issue with Spek. It looks like it...

# spek

[witoldsz]

Hello, I have an issue with Spek. It looks like it does share objects between tests within a file. In Java I was using JUnit and each test recreates everything, so there are no issues with some dirty state from test X leaking to test Y.
Am I doing something wrong?

[raniejade]

witoldsz: can you give an example?

[witoldsz]

OK, let me pick something…

[witoldsz]

object ForexRatesSpec: Spek({
    describe("ForexRates") {

        val mq = FakeMQ3()
        val setup = EnvSetup(mq, Config(…))

        val clock = ClockStub()
        val jooq = setup.jooq
        val txm = setup.ultm.txManager
        val db = MarketHistoryDatabase(jooq)

        beforeGroup {
            mq.connect()
        }

        beforeEachTest {
            txm.tx { jooq.truncate(FX_HISTORY).execute() }
            clock.setTime("2017-06-23T12:04:35.500Z")
        }

        on("first call") {
          …
        }

        on("subsequent calls") {
          …
        }
    }
})

[witoldsz]

If I move everything into before… then I will have much more typing: `val`s become `var`s etc…

[raniejade]

You could use memoized if you're at Kotlin 1.1

[raniejade]

val mq by memoized { FakeMQ3() }

[witoldsz]

But I want the opposite, I need fresh FakeMQ3 on each test

[raniejade]

by default each test will have a unique instance

[raniejade]

val mq by memoized(CachingMode.TEST) { FakeMQ3() }

[raniejade]

CachingMode.TEST is the default value

[raniejade]

GROUP and SCOPE are supported as well

[witoldsz]

OK, let me check it

[witoldsz]

It is working, but looks awkward 😕

[raniejade]

why does it look awkward?

[witoldsz]

You look at the code and everything not marked as memoized is actually memoized.

[witoldsz]

The only fresh instances are the ones with memoized

[raniejade]

well, true but we really don't have control to val mq = FakeMQ3()

[witoldsz]

JUnit has it right, it just creates test environment for each test.

[raniejade]

and every group's (describe, context, etcc..) lambda is executed once.

[witoldsz]

Looks like a legit reason to switch to JUnit 😕

[raniejade]

JUnit does it that way, spek does it this way.

[witoldsz]

Thanks for your help, I was wondering if I did not miss some configuration for this.

[raniejade]

Btw, the old way of doing this was by declaring your state as var and setting them up in a beforeEachTest.

[witoldsz]

That was on my mind as well. At least it makes thie setup clear as to what happens.

[raniejade]

problem with it is you need to declare the types as nullable

[raniejade]

so when using them you have to call them with !!

[witoldsz]

ah, true

[raniejade]

lateinit is not supported locally

[jk]

@witoldsz don't you end up with the same issue in Junit? you would have to declare var mq: FakeMQ3? = null and setup with @Before?

[witoldsz]

No, it will recreate the test on each test.

[witoldsz]

Working with it in Java for ages, with Kotlin I wanted to try something new.

[witoldsz]

Would it be possible to change Spek, so it would not share objects between tests? Maybe with some kind of configuration option, so it would not affect existing users?

[raniejade]

I don't think so, spek is very different from JUnit. First there is no notion of "spek instances", you can even use object to declare a spek. As you can also see, everything is setup-d using lambda blocks, no class instances there only local variables.

[raniejade]

Also, say your spek has 100 tests (`it`s declared) if we allow that we have 100 instances of that spec and we have to execute all the lambdas 100 times, since there is no way to know the test tree without executing it.

[witoldsz]

😞