andrewreitz / android-spock Goto Github PK

View Code? Open in Web Editor NEW

89.0 89.0 7.0 417 KB

Running Spock on Android

License: Apache License 2.0

Groovy 31.34% Java 68.66%

android-spock's People

Contributors

Stargazers

Watchers

Forkers

mg6maciej mariogarcia gsusie visiray-zz uam-moocandroid bschramke

android-spock's Issues

IndexOutOfBoundsException e = thrown() doesn't work

Using thrown causes all tests to not run.

Android is probably some missing some java class that we need.

More than an issue is just a question... Mostly all production environments are based on KPIs and that stuff, so a way to measure the "amount" and """quality""" of the tests are needed. Is it possible to integrate the tool with Jacoco coverage tool?

Create Javadocs

And put on github pages

Fix Dependencies of Library

Android libs doesn't seem to know how to attach dependencies in the pom creation. Do it by hands in publishing.gradle.

Instrumentation method test invocation

I have connected android spock according to your instructions in tutorial. Ordinary unit test works excelent, but when I want execute one instrumentation test method error occurs - Test running failed: No test results. Empty test suite.. Furthermore, when I execute all methods in instrumentation test class everything works fine. Please, let me know what information you need to solve the problem.

Setup dependencies

Setup Dependencies readme seems to be outdated.
I think this should be updated to: androidTestImplementation 'com.andrewreitz:spock-android:2.0.0'

Create Android Specification

To allow for getting activities and other android components.

Update to use spock 1.0

Wild Card Data Table Type Don't Work

They will compare false to whatever object type they are being compared against.

Can this execute espresso / robotium tests?

Hey,
This is more of a question then issue, but I'm wondering if I can use your runner for functional testing?
Cheers,
Maciej

Update Gradle.Properties

The license URL is wrong and version and group are not used.

Keep instrumentation and unit tests separate

Is there any reason why the tests "have" to be with the instrumentation tests in androidTest?

Problems using Espresso with android-spock

I tried to use espresso along with android-spock. This works fine, as long as my Specification has just one single test method.

If I add a second test which interacts with the activity, these second test hangs because it is waiting for the activity coming up.

I'm not sure if it's an bug or maybe I do something wrong? Or it's just a feature that is still not implemented?

I attached some sample code :
CalculatorActivitySpec.groovy is working perfectly fine.
OtherCalculatorActivitySpec.groovy the first test is passing, the second one hangs.

EDIT: I was able to solve the Problem. I was still on v1.2.1 and found that there is an attribute runMode introduced with v1.2.2. This is currently neither mentioned in the documentation nor the sample.

Add Documentation

Add some docs to the readme for the new stuff in 1.1.0