| commit | 27ee24a706655a9659e5de94cdc2b532ece20c25 | [log] [tgz] |
|---|---|---|
| author | hoisie <hoisie@google.com> | Wed Mar 17 17:29:34 2021 -0700 |
| committer | Michael Hoisie <hoisie@google.com> | Fri Mar 19 15:56:27 2021 -0700 |
| tree | fdcf247f8c08c0f89bce806ecbfa09cb0f050d50 | |
| parent | 46960fa18d7d2b71797d03d1c892754b92c22cb5 [diff] |
Add option to require valid image data in BitmapFactory.decode methods
It is currently impossible to write tests that depend on the error case of
BitmapFactory.decode methods. When invalid data is supplied to
BitmapFactory.decode methods in real Android, BitmapFactory is supposed to
return null and any provided BitmapFactory.Options.out{Width,Height} should be
set to -1. Currently Robolectric returns a Bitmap object with width and height
set to 100 in this case.
Add an new public API method ShadowBitmapFactory.setAllowInvalidImageData that
can be used to tweak this behavior. If
BitmapFactory.setAllowInvalidImageData(false) is called, BitmapFactory behaves
consistently with real Android by returning null and setting any provided
BitmapFactory.Options.out{Width,Height} to -1.
Long-term the goal is to BitmapFactory default is to to have
allowInvalidImageData=false, which is consistent with real Android.
PiperOrigin-RevId: 363545671
- integration_tests/ctesque/src/test/java/android/graphics/BitmapFactoryTest.java[diff]
- robolectric/src/test/java/org/robolectric/shadows/ShadowBitmapFactoryTest.java[diff]
- shadows/framework/src/main/java/org/robolectric/shadows/ShadowBitmapFactory.java[diff]
- .circleci/
- .github/
- annotations/
- buildSrc/
- errorprone/
- gradle/
- images/
- integration_tests/
- junit/
- pluginapi/
- plugins/
- preinstrumented/
- processor/
- resources/
- robolectric/
- sandbox/
- scripts/
- shadowapi/
- shadows/
- testapp/
- utils/
- .gitignore
- build.gradle
- CODE_OF_CONDUCT.md
- gradle.properties
- gradlew
- gradlew.bat
- LICENSE
- README.md
- resources.arsc
- settings.gradle
- WORKSPACE
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.
Usage
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.
Install
Starting a New Project
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.
build.gradle:
testImplementation "org.robolectric:robolectric:4.5.1"
Building And Contributing
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
Using Snapshots
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.
build.gradle:
repositories { maven { url "https://oss.sonatype.org/content/repositories/snapshots" } } dependencies { testImplementation "org.robolectric:robolectric:4.6-SNAPSHOT" }