We shadow Fragment as workaround to prevent some errors in onCreate for fixing b/135086559. This CL tried to not mock everything for fragment. We need to use correct way to create fragment lifecycle, so it can avoid some errors likes b/135086559. Test: atest MyDeviceInfoFragmentTest Fixes: 135086559 Change-Id: I0d650bc700f570114861081d537f83a3ba14147b
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.