Hi @hhariri, I am new to Kotlin but I really like what I see and have been exploring the testing framework options. I like the look of Spek but it took me a while to find the 1.0.x releases and to work out how to use them (before I found the 1.0 branch and samples). I don’t have a huge amount of time to spare but I’d be happy to try and help with any particular issues blocking you from publishing 1.0.

I wondered about https://github.com/JetBrains/spek/issues/52 (as something that my team would probably notice and grumble about)

@michaelbannister: Thanks! I’d love some help. And yes, that’s one issue that needs solving, along with the site, and actual release.

There is no showstopper, even not in urgency, so if it’s in time for end of june (or even before), I can wait.

@hhariri: please make notification in this channel when you’ll be ready for alpha testers of 1.0, me and my coworkers are interested in Spek and we can try in on production Android project written in Kotlin

@jcomo has left the channel

I also would love to try this in my open source project. I will definitely be in for alpha testers.

@artem_zin, @kittinunf you probably might want to also try out https://github.com/raniejade/kspec (I’m the author btw).

raniejade: kspec looks nice. one question: why does it evaluate logic in the describe block eagerly? i think code in describe blocks should work like beforeEach. also I think rspec does it that way

@christophsturm: it would be impossible to collect the

it

blocks if we don’t do it that way.

That’s why

beforeXXX

and

afterXXX

are provided.

i wonder why it works in scalatest

I guess it’s something that scala, but not in kotlin

it could evaluate the context block at startup to get the test names, and then evaluate them again for every test

Untitled.scala

@raniejade: in that snippet server can be immutable. if i initialized it in beforeEach, it would have to be a var

ahhhh

see https://github.com/raniejade/kspec/issues/25

🙂

ok but if i declare it lazy it should be possible with kotlin 1.0

lazy is for var only I think

not for val

sorry forget my previous statements

lazy is not supported for local variables

for our next project we were on the edge between scala and kotlin. i was pushing for kotlin but in the end we are now using scala because we found no testing framework thats as mature as scalatest

JUnit still works though 😉

one thing that is a must for us is running tests multithreaded.

scalatest can do that, even inside idea

testng can do it too, but it does not create a new test instance for each test so its hard to find a place where to store the objects that you set up. also the idea test runner gets confused when you run testng multithreaded

@cedric: ^^