Before the JUnit test suite was a blocking presubmit, new junit tests would be written without removing the old robolectric test. Now that the JUnit tests are productionized, we can remove the robolectric tests if there is also an associated Junit one. Utility script which was used to generate this list can be found at https://paste.googleplex.com/5113068112576512. Bug: 175389659 Test: atest SettingsUnitTests Change-Id: Iabf4dbcccd573e9e1482b3a3e61c0f169f81bcb4
Running Settings Robolectric tests
The full suite
$ croot
$ make RunSettingsRoboTests
Running a single test class
$ croot
$ make RunSettingsRoboTests ROBOTEST_FILTER=<ClassName>
For example:
make RunSettingsRoboTests ROBOTEST_FILTER=CodeInspectionTest
You can also use partial class name in ROBOTEST_FILTER. If the partial class name matches multiple file names, all of them will be executed.