Unit tests on Travis CI server are not reliable although I'm able to run them locally without problems. They require device emulator on CI. Moreover, I was able to run test coverage with codecov.io once what requires passing tests. Behavior of the unit tests using RxJava on CI server is non-deterministic. Right now, we have problems with PrefserObservablesTest. Initial travis configuration with tests and code coverage is included in .travis.yml.tmp file.
Some tests with observables sometimes throw the following error:
java.util.NoSuchElementException: No event found while waiting for OnNext
at com.github.pwittchen.prefser.library.utils.RecordingObserver.takeEvent(RecordingObserver.java:61)
Possible fixes:
Create custom test runner, set it for tests with RxJava and add additional permissions to Manifest (it was mentioned somewhere inside the issues of RxBinding project). Unfortunately, I don't want to add additional permissions for library, so probably I'll create separate module called testing-utils like in RxBinding project to make it work.
Unit tests on Travis CI server are not reliable although I'm able to run them locally without problems. They require device emulator on CI. Moreover, I was able to run test coverage with codecov.io once what requires passing tests. Behavior of the unit tests using RxJava on CI server is non-deterministic. Right now, we have problems with
PrefserObservablesTest
. Initial travis configuration with tests and code coverage is included in.travis.yml.tmp
file.Some tests with observables sometimes throw the following error:
Possible fixes: Create custom test runner, set it for tests with RxJava and add additional permissions to Manifest (it was mentioned somewhere inside the issues of RxBinding project). Unfortunately, I don't want to add additional permissions for library, so probably I'll create separate module called testing-utils like in RxBinding project to make it work.
content of initial
.travis.yml
file