ElectricSpock

What's new

The latest version is 0.6

Version 0.6 supports @Config annotation of Robolectric, and tested with Robolectric 3.4.2.

Version 0.5 Compatible with Robolectric 3.3.x. Reorganize yet again, maximal reuse of code from RobolectricTestRunner

Version 0.4 reorganize code structure, new ElectricSuite class

Version 0.3.1 fix an issue to build with jitpack.

Version 0.3 is built as JAR rather than AAR to make gradle detect ElectricSpecification as JUnit class properly.

Version 0.2 is updated to work with Robolectric 3.2.

For those who stick to Robolectric 3.2, please use version 0.4.1.

For those who stick to Robolectric 3.1, please use version 0.1.

About

The Android test framework Robolectric is designed with JUnit in mind and it does not work well with Spock framework. Fortunately there is a project RoboSpock is designed for that. It configure Robolectric properly under the framework of Spock framework. However it based on some internal source code of Robolectric and it has no official support to Robolectric 3.1 yet. There is an issue for that, but it has been quite some time. So I decided to make my own.

It is heavily based on RoboSpock project. It borrow a lot of code from there, and make some tweak of my own. This project is never possible without the excellent foundation.

Current version (0.6) of the library is tested with Robolectric 3.4.2.

Installation (Gradle)

The archive of this project is deployed with jitpack. Add the following to your gradle build script.

Add it in your root build.gradle at the end of repositories:

 allprojects {

repositories {

 ...
 maven {
 url 'https://jitpack.io' 
}

}
  
}

Add the dependency

 dependencies {

testCompile 'com.github.hkhc:electricspock:0.6'  
}

Spock, Robolectric and Groovy are dependencies of ElectricSpock, so it should work without adding these dependencies to build.gradle, but you may override them with the version you prefer.

Then we may just write Spock specification with ElectricSpecification class and Robolectric's @Config annotation

@Config(constants=BuildConfig) class MySpec extends ElectricSpecification {

def "Robolectric is enabled"() {

 when: "invoking call to Android API"

 android.util.Log.d("TAG", "Hello world")

 then: "there should not be any error"

 notThrown Exception

}
  
}
 

ElectricSuite

The class ElectricSuite is a helper class to help organize test methods of Specification into group. It is essentially a test class with Suite runner. However we don't need to use @SuiteClasses annotation to specify test classes. Instead the class scan all static inner class as test classes.

For example

class MySpec extends ElectricSuite {

static class MyInnerSpec1 extends ElectricSpecification {

[....]
  
}

static class MyInnerSpec2 extends ElectricSpecification [

[....]
  
}
  
}
 

Please note that there are a few limitations:

• We cannot have any test method in the ElectricSuite class. All test methods shall be in the inner test classes of ElectricSuite.

• (ElecrtricSpock 0.5 fixed this) When using with Spock-reporting-plugin, all inner classes of the same ElectricSuite class shall have the same base class. i.e. Either all of them extend from ElectricSpecification or Specification. Mix of different base classes will cause exception in the reporting plugin. It will be something like OverlappingFileLockException.