Files

tmfang d5405cf49d Fix InstantiationException on fragment

Since we overrided the empty constructor,
it can't find a empty constructor when
Fragment tries to instantiate a fragment
in framework.

So, we can't override this constructor,
and then just use newInstance() to initialize
and setup a new Fragment.

Test: robotest
Change-Id: Ifcd1c1771bc69d947caeee5c5bc055c4f94365c2
Fixes: 115676209

2018-10-17 04:20:09 +08:00

assets

Add version 2 of AppDataUsage.

2018-09-27 16:53:31 -07:00

config

Move ShadowXmlUtils to settingslib

2018-09-11 12:54:23 -07:00

res

A new attribute which can show the dynamic summary

2018-09-26 17:48:12 +08:00

src/com/android/settings

Fix InstantiationException on fragment

2018-10-17 04:20:09 +08:00

Android.mk

Use settingslib shadows in Settings robotest

2018-05-30 14:36:26 -07:00

OWNERS

…

README.md

…

README.md

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.