Offer baseline `RavenwoodFlagsValueProvider`.
Many test authors are starting to use `CheckFlagsRule` across suites like CTS, so instead of recommending that they use `null` when on Ravenwood, offer them a clear behavior that is either "all-on" or "all-off". Eventually we'll explore providing default flag values on Ravenwood, but let's get something cleaner available now. Bug: 318841620 Test: ./frameworks/base/ravenwood/run-ravenwood-tests.sh Change-Id: Id234a375426fad38f64d3a999339bb720eae84bf
Showing
- Ravenwood.bp 3 additions, 0 deletionsRavenwood.bp
- core/tests/coretests/src/android/os/PowerManagerTest.java 3 additions, 1 deletioncore/tests/coretests/src/android/os/PowerManagerTest.java
- core/tests/coretests/src/android/os/WorkDurationUnitTest.java 3 additions, 1 deletion.../tests/coretests/src/android/os/WorkDurationUnitTest.java
- ravenwood/Android.bp 17 additions, 0 deletionsravenwood/Android.bp
- ravenwood/junit-flag-src/android/platform/test/flag/junit/RavenwoodFlagsValueProvider.java 54 additions, 0 deletions...platform/test/flag/junit/RavenwoodFlagsValueProvider.java
- ravenwood/test-authors.md 18 additions, 0 deletionsravenwood/test-authors.md
Loading
Please register or sign in to comment