<@U12GDSSVC> I would suggest to start with separate `on(”true”) { it(”does c”) {} } on(”false”) { it...

# spek

[artem_zin]

@sboishtyan I would suggest to start with separate on(”true”) { it(”does c”) {} } on(”false”) { it(”does d”) {} and once you feel comfortable with that — use more complicated things and reduce boilerplate, you’ll naturally find solutions that’ll fit your coding style since Spek tests are just kotlin code in a giant lambda expression

[sboishtyan]

artem_zin: thx

[artem_zin]

@sboishtyan np, I’ll share a little bit experience learned from using Spek for about a year now in our team: sometimes we try to rethink over complicated specs that involve lots of own dsl extensions that reduce boilerplate and fall back to plain-old simple specs, feels so great.

Hope you’ll be able to find balance of boilerplate vs simplicity!

[sboishtyan]

That's great. Where do you want to share your experience, blog or conference may be?

[artem_zin]

@sboishtyan damn, can’t get used to Slack Threads yet, I’ve already shared some of it on 2 conferences in Russian (I can share links if you want), no plans for English variants yet