| b2ff57b17efb727c24b096ac7b1d7f8870bf1bde |
|
11-Feb-2017 |
Maurice Lam <yukl@google.com> |
Use constants=BuildConfig.class for robolectric
In robolectric tests, use @Config(constants=BuildConfig.class), which
is the "gradle way" to configure Robolectric. Added the hacks that
are needed to make that happen in our setup, like
PatchedGradleManifestFactory and the custom build directory lookup.
Having this change allows Robolectric tests to run against merged
resources, which means different build variants will now resolve
resources correctly. Previously a test would fail in, say, resolving
@style/SuwThemeGlif.
Also migrated GlifDimensionTest to run on Robolectric.
Test: ./gradlew test
Change-Id: Ia7231f95818891a649678a0a6da0220a44031bf7
/frameworks/opt/setupwizard/library/test/robotest/src/com/android/setupwizardlib/span/LinkSpanTest.java
|
| 199cec9d40aef7ac34dd0cd4badae4eb2e7373c5 |
|
29-Dec-2016 |
Maurice Lam <yukl@google.com> |
Migrate PartnerTest to Robolectric
Since PartnerTest depends on resources, add BaseRobolectricTest class
to configure the manifest (and the SDK version).
In addition, to work around a Robolectric issue, add dependency on
Open GL API.
Test: ./gradlew test
Bug: 32975598
Change-Id: I41a8099197412ce6353c1920fb7b59d83fb7c9d5
/frameworks/opt/setupwizard/library/test/robotest/src/com/android/setupwizardlib/span/LinkSpanTest.java
|
| 2e634640f3ed1b101f3748849b415fa14d57991c |
|
29-Dec-2016 |
Maurice Lam <yukl@google.com> |
Add robolectric test
Configure the build target and migrate LinkSpanTest to Robolectric.
Move existing instrumentation tests into test/instrumentation
Bug: 32975598
Test: ./gradlew test
Change-Id: I9bb39142c616a2c44fe38f48d92e89ab8ebda7ba
/frameworks/opt/setupwizard/library/test/robotest/src/com/android/setupwizardlib/span/LinkSpanTest.java
|