Android developer portal with tools, libraries, and apps
An A/B Testing Library for Android that makes writing simple tests simpler by using annotations.
Deploy new features to a choosen percentage of uers before delivering it to everyone.
It's useful to see if the new feature is appreciated by users, and do some adjustment before the grand opening.
This library allows you to run Android UI tests multiple times in a single instrumentation execution. Written in Kotlin.
A complete reference for Android Testing with examples.
Despite the annual improvement of tools — everything related to Android instrumented testing still can be challenging and requires a lot of attention from engineers.
The goal of this open-source documentation is to make the process of introducing instrumented testing into your team smoother and avoid repeating our mistakes.
Simple tool which help you to implement A/B Test.
Droidcon 2013 Gradle workshop is an example project. It shows how to write Unit and Integration tests.
The goal of this project is to speed up the setup of Robolectric, Robotuim, Roboguice, and Mockito in Android Studio. Since there is not built in support for Robolectric there is a lot of manual set up that has to be done. This project uses Robolectric-gralde plugin as well as his InjectedTestRunner.
A sample android starter project to demonstrate the integration of the following tools:
- Automation: Gradle
- Testing: Android Testing Framework, Robotium, Roboelectric (JUnit, Android)
- Continuous Integration: TravisCI
Sample Tasks:
- Adding testing-only project dependencies
- Using square spoon to run integraton tests
- Writing android tests with robotium
- Writing junit tests with robolectric
- Android tests can be run with only Robotium use "gradle connectedAndroidTest"
- Android tests can be run with Robotium and Spoon "gradle spoon"
- Robolectric junit tests can be run with "gradle clean test"
AndroidTestingPlease is an Android project that uses Robolectric and Espresso for testing and Gradle to build.
Appium is an open source test automation framework for use with native and hybrid mobile apps. It drives iOS and Android apps using the WebDriver JSON wire protocol.
Burst is a set of test runners which rely on enums for varying both the instantiation of test classes and the methods inside of them.
A sweeter Espresso. Never write your own IdlingResource again. Never manually turn off system animations again.
A library for testing javac compilation with or without annotation processors.
Simple class created in order to make Android automation testing easier, faster, cleaner and more intuitive. It synchronizes operations that might occur on any thread - with test thread. ConditionWatcher can be used as a replacement to Espresso's IdlingResources or it can work in parallel with them.
A collection of examples demonstrating different techniques for automated testing with Espresso.
Fork is the fastest way to execute Android instrumentation test suites by Shazam developers.
Gordon is an Android instrumentation test runner designed for speed, simplicity, and reliability, so you can plug it in and never worry about flaky UI tests again.
Green Coffee is an Android library that allows you to run Cucumber scenarios in your instrumentation tests.
Allows to use green-coffee together with Android Test Orchestrator.
Want to assert that class has private constructor? Let's do it!
This repository contains examples of basic unit tests written in Kotlin. In specific directories you can find gradle buildscript with needed dependencies and configuration, simple unit test and parameterized test.
A helper class that implements both an Espresso IdlingResource and an OkHttp 2 and 3 Interceptors.
Testing and validation of REST services in Java is harder than in dynamic languages such as Ruby and Groovy. REST Assured brings the simplicity of using these languages into the Java domain.
Restito is a tool which is inspired by mockito and functionally is diametrically opposite to the Rest Assured.
Restito provides a DSL to:
- Mimic rest server behavior
- Record HTTP calls to the server
- Perform verification against happened calls
Espresso's consistency makes it really easy to learn.
Want to match a view with a specific id? Use withId(R.id.some_id). Need to match with a piece of text? Use withText(R.id.some_text) or withText("some text). Awesome, consistent and it's very clear what it is you are doing.
However...
After a few hours writing test code you'll find your code being a little bit too verbose. Not anymore.
Why should you need to explicitly specify that you are matching with some text if you are passing in some text as a parameter? Some for the view id, you can already see that it is a view id.
Ristretto allows you to write the same test code as you already write, but less verbose.
Robolectric is a unit test framework that de-fangs the Android SDK jar so you can test-drive the development of your Android app. Tests run inside the JVM on your workstation in seconds.