Add InstrumentFragment for non-PreferenceFragment types.
This allows app fragment use a less heavyweight fragment as super class if they don't need PreferenceFragment. Using this class as base is generally easier to set up robolectric tests too. Bug: 33354536 Test: RunSettingsRoboTests Change-Id: I91c4d242ea0333c76c8767c03c3f18dee6b6e104
This commit is contained in:
@@ -41,12 +41,12 @@ import com.android.internal.logging.nano.MetricsProto.MetricsEvent;
|
||||
import com.android.settings.R;
|
||||
import com.android.settings.SettingsActivity;
|
||||
import com.android.settings.Utils;
|
||||
import com.android.settings.core.InstrumentedFragment;
|
||||
import com.android.settings.core.InstrumentedPreferenceFragment;
|
||||
import com.android.settings.search.Index;
|
||||
|
||||
import java.util.HashMap;
|
||||
|
||||
public class SearchResultsSummary extends InstrumentedFragment {
|
||||
public class SearchResultsSummary extends InstrumentedPreferenceFragment {
|
||||
|
||||
private static final String LOG_TAG = "SearchResultsSummary";
|
||||
|
||||
|
||||
Reference in New Issue
Block a user