Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests for Android #74

Closed
franzejr opened this issue Nov 30, 2015 · 2 comments
Closed

Tests for Android #74

franzejr opened this issue Nov 30, 2015 · 2 comments

Comments

@franzejr
Copy link
Contributor

This Application will have tests? Feature tests?

Probably https://github.com/robotiumtech/robotium is a good one idea.

@franzejr
Copy link
Contributor Author

@Viirus, @negue , something in mind ?

@dlew
Copy link
Contributor

dlew commented Dec 16, 2015

Some information about testing...

Robotium is somewhat of an older project. Nowadays the recommended framework is Espresso (from Google). You can find out a lot more about that here: https://google.github.io/android-testing-support-library/

Generally speaking, the more unit tests you can have work without Android, the better (since pure Java unit tests are far faster). I'm not actually a big fan of integration tests because they're slow and brittle (any change to the UI can cause a problem). Testing the logic of the app quickly would be a good start.

Since the app is open source, you can use Travis CI for free on it. The neat thing about that is that you can apply tests automatically to every pull request, which can act as a filter on bad PRs. For example, see RxBinding's current PRs, where one of them is currently failing to pass: JakeWharton/RxBinding#128

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants