Status: Untriaged
Owner: ----
CC:
mmel...@google.com,
ha...@chromium.org,
mthi...@chromium.org Components: Internals>Flags
OS: Android
Pri: 3
Type: Task
New issue 1335923 by
hnaka...@chromium.org: Add Features.JUnitProcessor to BaseRobolectricTestRunner
https://bugs.chromium.org/p/chromium/issues/detail?id=1335923Features.JUnitProcessor processed @EnableFeatures and @DisabledFeatures and resets flag overrides and cached flag returned states for testing. It is a common pitfall to forget to include in in a Robolectric test.
The blocker for this change is that Features.JUnitProcessor is Chrome-layer, while BaseRobolectricTestRunner is base layer. We could solve this by either:
- Creating a derived ChromeRobolectricTestRunner and mass migrating tests in Chrome to it.
- Moving CachedFeatureFlags to base (which requires removing sDefaults by implementing
go/clank-flags-before-native)
I favor moving CachedFeatureFlags to base.
--
You received this message because:
1. You are auto-CC'd on all issues in component Internals>Flags
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settingsReply to this email to add a comment or make updates.