Skip to main content

Running Android Unit Tests

Application tests are essential when it comes to improving and maintaining product quality and performing routine checks which are difficult for humans to perform regularly.

Unit tests are usually considered first as they run really fast and are relatively easier to write and measure.

We will create a local unit test here as an example and show you how to run the test during your build process.

Creating unit tests

First, please add test dependencies to your build.gradle file:

dependencies {
// Required for local unit tests (JUnit 4 framework)
testImplementation 'junit:junit:4.12'

Create your test file in your project’s module-name/src/test/java/ folder.

package com.example.appcircle_sample_android;
import org.junit.Test;
import static org.junit.Assert.*;

* Example local unit test, which will execute on the development machine (host).
* @see <a href="">Testing documentation</a>
public class URLValidatorUnitTest {

public void invalid_url_test() {
boolean isValid = URLValidator.isValid("http:/");

public void valid_url_test() {
boolean isValid = URLValidator.isValid("");

This example checks to see if the provided URL is valid.

Running your unit tests in Appcircle

To run your unit test during the build process, you can simply use a custom script in your build profile.

Simply go to your build workflow and add a custom script after the Sign Application step.

See the following page on our documentation to learn more about creating custom workflow steps:

File IconWorking with Custom Scripts

Add the following Bash script to your custom script step:

set -ex
./gradlew test
mv app/build/reports/tests $AC_OUTPUT_DIR
mv app/build/test-results $AC_OUTPUT_DIR

This simple Bash script will trigger your unit test and output the test results to be packed along with your binary files. You will get the test results both in xml and html formats.