Are there limitations around using annotations for...

# spek

[mkporwit]

Are there limitations around using annotations for Spek test classes? I'm trying to leverage com.github.trevershick.test.ldap, which can take an annotation to additionally configure the LDAP instance. This annotation works fine in JUnit (4 and 5) based tests, but appears to break with Spek.

@LdapConfiguration(ldifs = arrayOf(Ldif("/hoyluPersonTestSchema.ldif")))
class LdapHandlerSpec : Spek({
    val ldapServer = LdapServerResource(this)

[raniejade]

can you try using object instead of class and change LdapServerResource(this) to LdapServerResource(LdapHandlerSpec)?

[mkporwit]

let me see...

[mkporwit]

OK, that appears to do the trick.

[mkporwit]

Can you shed some light into that difference?

[mkporwit]

And once again, @raniejade, you're a legend

[raniejade]

Nice, this doesn't refer to the spec instance - it refers to the receiver of the top level lambda.

[raniejade]

Spec instances doesn't matter in Spek, that's why you can use object instead of class.

[mkporwit]

I think that's a little more cryptic than I can currently understand... I get that the body of my test suite is a lambda passed into the constructor of Spek... but isn't the receiver of that the LdapServerSpec, which derives from Spek?

[raniejade]

Nope, abstract class Spek(val spec: Spec.() -> Unit). https://github.com/spekframework/spek/blob/1.x/spek-api/src/main/kotlin/org/jetbrains/spek/api/Spek.kt

[raniejade]

then https://github.com/spekframework/spek/blob/1.x/spek-api/src/main/kotlin/org/jetbrains/spek/api/dsl/Spec.kt

[mkporwit]

OK. I'll need to poke through that at some saner hour.

[mkporwit]

For now, much obliged for the pointer and for the help in getting me unstuck.

[mkporwit]

If you're ever in Seattle, beers (or whatever is your fancy) are on me.

[raniejade]

No worries, let me know if you have more questions 🙂