Why not publish to jcenter? It's really easy

and you don't have to deal with all the extra hoops that Maven Central makes you jump through

@apatrida: snapshots are now on jetbrains.jfrog.io/jetbrains/spek-snapshots. @cedric releases will be on jcenter and maven.

hi guys, how to run tests in command line? (spek tests) i have to run them on CI

@dmitriy.m: are you using any build tool? Like gradle or maven?

@dmitriy.m: you should be able to run Spek tests as other regular tests in your project, for Android Gradle projects it’s

./gradlew test

for JVM tests and

./gradlew connectedAndroidTest

for instrumentation tests

Yep, I've resolved this tasks, thank you guys

hi! started to use

Spek

and have a few questions (maybe known things, didn't find answers): 1) Currently not able to do "right click + Debug" on test in IntelliJ (Android Studio to be exact) - is this going to be supported later? 2) Not able to double click test + go to place where it is defined 3) I get a feeling that running spek tests is currently slower than junit ones - am I right? if yes, how soon speed is gonna be addressed? (I'm not quite sure if I'm right, because I don't have much tests now to run) I'm using

describe/it

specifications

forgot to mention that I am using

1.0.25

version

1) doesn’t work at the moment, you can use

fit

,

fon

and other

f*

to run specific test/subtree 2) Double click where? 3) We have some non-0 amount of Spek tests and didn’t notice performance regression in compare to JUnit4

oh, didn't know about fit/fon

double clicking in tool window's test list. where the green icons on the left of passed tests along with their names

same thing which I would right click in 1)

don't have a setup to make screenshot from at this computer 🙂

got it, yeah Spek has no support from IDE yet, so yeah

I see, thanks! Reading above about spek transitioning to junit5, I got another question: do you know by chance if this will have some sideffects when using spek for writing android unit-tests?

@dimsuz: We’re hoping to improve navigation and single execution of tests and it’s one reason we’re moving to junit5. Hopefully we’ll do this for the 1.0, even if it means delaying it a little bit. In regard to android unit tests, are you talking integration?

@dimsuz: moving to JUnit5 won’t affect “unit” (or better call them JVM) tests for Android projects, but will affect instrumentation tests. Mainly because JUnit5 uses Java8 APIs

@hhariri: no, was talking about JVM tests. Artem pointed out a more correct name, and provided an answer above.

and for android integration we would probably need to resort to junit4 I guess. Didn't check if junit4/5 are co-installable yet...

@dimsuz: so you’re also using Spek for integration tests right now?

not yet, only started a new project, using Spek for unit tests, but trying to look into the future...

@hhariri: we do

it works and I’m happy and unhappy about it at the same time

shrodinger-happy

@artem_zin: could you expand on your feelings there? 🙂

@hhariri: Things I like about Spek (applies to any kinds of tests): 1. Allows nesting configurations trees which saves from boilerplate we had with JUnit 2. Allows post-TDD when you write

on()

, then

it()

then run, check that it fails and then add

beforeEach

to

on()

and check that it passes. Much more natural ~TDD for me. Things I don’t like: 1. Messed up reports, both in IDE and in report files. Instrumentation tests has negative time duration, most of the test cases have name

null

. 2. No local delegates makes handling “environment" hard (Kotlin 1.1 will have that) 3. No IDE support

3 we’re working on

1 is that logged?

@hhariri: you mean is that in your issue tracker?