commit | a8dec810280e8c00bbec1f05428c9c44aa4643f3 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Thu Mar 05 13:40:53 2020 -0800 |
committer | Copybara Robolectric Bot <copybara-robolectric@google.com> | Thu Mar 05 13:41:26 2020 -0800 |
tree | 54f7dec9674892da82ce83b966270747354658db | |
parent | 71557ad8872dd4cf269a650e78af35f319a58fb3 [diff] |
Fix permission check when matching broadcast receivers Context.registerReceiver() specifies a permission the broadcaster must hold to send the intent ("BP"). Context.sendBroadcast() specifies a permission the receiver must hold to receive the intent ("RP"). Until now, Robolectric broadcast dispatching would find receivers whose required broadcaster permission matched the broadcaster's required receiver permission ("BP == RP"); after this bugfix, broadcast dispatching checks the broadcaster and receiver for required permissions from the test manifest. This change keeps the old codepath around in order to avoid breaking existing tests that don't include a test manifest (thus wouldn't pass the fixed permission check) but happen to work because the two required permissions are equivalent. PiperOrigin-RevId: 299182290
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.3.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 install compileTest
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.4-SNAPSHOT" }