👍

@jasper this might interest you as well https://github.com/JetBrains/spek/issues/87

Thanks. I think that’s what I was looking for. Voted it.

Hi everyone. I've just created a gradle based kotlin project in intellij idea community, but I don't manage to set up Spek inside it, though I declared it in build.gradle.

Build_gradle_used_when_trying_to_load_spek.groovy

Gradle could not find the spek plugin.

You're missing:

repositories {
        mavenCentral()
        maven {
            url "<http://repository.jetbrains.com/all>"
        }
    }

There should be another repositories block outside of buildscript

btw Spek master is resolving via jitpack completely fine

repositories {
        mavenCentral()
        maven { url "<https://jitpack.io>» }
}

dependencies {
    testCompile "com.github.JetBrains:spek:master"
}

I found this a bit more useful due to the absence of versioning hassle.

@yuriy.yarosh: that’s not great practice because you’re not pointing to specific version your build maybe broken at any time

I’m completely fine with running the master branch of the spek, although folks should provide some git tags, so specific versions could be targeted via jitpack …

@raniejade: Thank you very much. Now gradle process does not complain 😀

Uploading to JCenter is really straightforward, and like @artem_zin points out, this way you control what releases users can download

even uploading to maven central is not that painful

With all the PGP and Javadoc nonsense, it's pretty painful, especially on Windows

Javadoc is made worse on Kotlin, have to create an empty javadoc jar file just to placate Maven Central

@cedric: I think I uploaded one thing to maven central and gave up trying after that. Later on JCenter got popular and they make it really easy to publish things.

Like, I had to file an issue on their JIRA or whatever to add a new package. Really?

Running tests I get the error:

!!! JUnit version 3.8 or later expected:

I’ve moved Junit up in the .iml file, however I’m sure this is not the correct solution. Hints? New to Android development

I'm guessing one of your dependencies is pulling an older JUnit (a sign you should get rid of that dependency ASAP)

hmmm.

gradle dependencies

shows me no evidence of JUnit < v4. And the problem occurs in IntelliJ (preferred) but not Android Studio.

Though I might have observed it in Android studio before? (can’t recall with 100% certainty).

If you're using Gradle you shouldn't normally need to touch the .iml file. You may want to try refreshing the project from the Gradle toolbar?

Also: does it work if you run

gradle test

at the command line rather than inside IntelliJ?

hi all guys. i need some help with

Spek

and

kotlin

i have unit test with

@Rule
    val folder = TemporaryFolder()

but inside my spek test i cannot have access to it( if i put it inside

companion object

, it cannot be initialzed correctly

With Spek you don’t really need JUnit rules, Spek by design has hierarchical structure where you can put your “rules” in

on/given/context

blocks

@artem_zin: how it could look like?

on {
 @Rule
….
}

?

I___m_not_sure_if_it___ll_work_but_you_can_try_to_put_your_JUnit_rules_to_after_Spek_closure_.kt

@dmitriy.m: I mean you don’t need JUnit rules with Spek

it gives me error while i’m trying to create file