Add strict_mode: false

As strict mode is in place, the default strict_mode is now set to true. We are encourage teams to write tests in strict_mode to make tests Bivalent (able to run on device and devicelessly)
For more info on strict mode: go/roboStrictMode
Also fixed some missing deps.

Flag: NONE
Test: atest Launcher3RoboTests
Bug: 334089788
Change-Id: I4b4f2ef9a21926eef63fcada81355b928bbe2870
Merged-In: I4b4f2ef9a21926eef63fcada81355b928bbe2870
This commit is contained in:
Kevin Liu
2024-06-19 15:50:28 +00:00
parent cc71aa83e1
commit 97cbdbcfd3
+7
View File
@@ -241,11 +241,17 @@ android_robolectric_test {
java_resource_dirs: ["config"],
static_libs: [
"flag-junit-base",
"flag-junit",
"com_android_launcher3_flags_lib",
"com_android_wm_shell_flags_lib",
"androidx.test.uiautomator_uiautomator",
"androidx.core_core-animation-testing",
"androidx.test.ext.junit",
"androidx.test.espresso.core",
"androidx.test.espresso.contrib",
"androidx.test.espresso.intents",
"androidx.test.rules",
"uiautomator-helpers",
"inline-mockito-robolectric-prebuilt",
"platform-parametric-runner-lib",
"testables",
@@ -261,4 +267,5 @@ android_robolectric_test {
],
instrumentation_for: "Launcher3",
upstream: true,
strict_mode: false,
}