commit | 837f92ab866010129697ca8171ef61c2124e51a2 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Wed Apr 14 19:12:22 2021 |
committer | Michael Hoisie <hoisie@google.com> | Sat May 08 19:09:06 2021 |
tree | e0934754476a4a0c109fcce2e4a78b76fd1a709d | |
parent | 999aa6e510eef5ff40724c188eacc992cd3c5820 [diff] |
Update ShadowPhone to use the call list in Phone Instead of overriding the call list in the shadow, use the internal one in Phone. Adds methods to the ShadowInCallService to expose handler methods so that we may bind an InCallAdapter to the ShadowInCallService, which allows a more realistic way of adding and updating calls using a ParcelableCall as input. PiperOrigin-RevId: 368480951
Robolectric is the industry-standard unit testing framework for Android. With Robolectric, your tests run in a simulated Android environment inside a JVM, without the overhead of an emulator.
Here's an example of a simple test written using Robolectric:
@RunWith(AndroidJUnit4.class) public class MyActivityTest { @Test public void clickingButton_shouldChangeResultsViewText() throws Exception { Activity activity = Robolectric.setupActivity(MyActivity.class); Button button = (Button) activity.findViewById(R.id.press_me_button); TextView results = (TextView) activity.findViewById(R.id.results_text_view); button.performClick(); assertThat(results.getText().toString(), equalTo("Testing Android Rocks!")); } }
For more information about how to install and use Robolectric on your project, extend its functionality, and join the community of contributors, please visit http://robolectric.org.
If you'd like to start a new project with Robolectric tests you can refer to deckard
(for either maven or gradle) as a guide to setting up both Android and Robolectric on your machine.
testImplementation "org.robolectric:robolectric:4.5.1"
Robolectric is built using Gradle. Both IntelliJ and Android Studio can import the top-level build.gradle
file and will automatically generate their project files from it.
Robolectric supports running tests against multiple Android API levels. The work it must do to support each API level is slightly different, so its shadows are built separately for each. To build shadows for every API version, run:
./gradlew clean assemble testClasses --parallel
If you would like to live on the bleeding edge, you can try running against a snapshot build. Keep in mind that snapshots represent the most recent changes on master and may contain bugs.
repositories { maven { url "https://oss.sonatype.org/content/repositories/snapshots" } } dependencies { testImplementation "org.robolectric:robolectric:4.6-SNAPSHOT" }