this is still the same type

and you cannot nest tests inside each other anyways.. ot at least you should not

But usually you only need part of the description string, so you'll have to cut it up...

true.. but i also have just so slighty varrying tests that anything else with iterating through lists would not work

That's where test data shines, you have all of it split into fields, and can generate the description from it easily... and for the slight varieties, Kotlin has Lambdas...

maybe if it were the same data and different operations i could make a list of Functions..

So they could be saved in the test data

but in thoise case the data would not even generate the strings i want..

Why?

it just slightly different.. { "key": "value" } vs key: value that i want in the output

but i still think having a shorther description and being able to reuse that in the message of the assert ot make a longer description there might be useful

when you have more than one assert per test block

i thin thats discouraged though

description "test feature a" assert(something, "$description and more specifics")

You can have multiple

it() {}

in the same group, probably better than putting all the asserts together...

yes thats what i do

single assert per test

That's I think the best... You could also try #atrium, it gives very good assertion failure feedback

It won't do high level stuff, but that should probably be in a separate

it

anyways... but if you're checking multiple things for one high level concept it does a great job!

sexy

i will first port all the Junit 4 tests to spek2 usin kotlin tests though and get feedback on that

Good luck 🙂

i do not get why he function had to be named it.. it causes problems with loops and lambdas

I'm just trying to set up spek2 with the plugin in Android Studio. Is this supported ? I can't seem to get it to work nor can I find a good tutorial or docs for doing that...

i don't think anybody tried to use it with android yet, or only using the gradle plugin

just got it to work, after updating Android Studio to 3.2, and Kotlin to 1.2.71.

Was quite frustrating before, nothing Spek-related was showing up on the UI, but no errors either.

There's a plugin update as well: https://plugins.jetbrains.com/plugin/10915-spek-framework - just waiting for Jetbrains to approve the update.