Closed
Bug 1098575
Opened 10 years ago
Closed 7 years ago
Basic test for search activity
Categories
(Firefox for Android Graveyard :: Search Activity, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Margaret, Unassigned)
References
Details
I filed bug 1072429 about moving SearchEngineTest to mozilla-central, which tests the search engine parsing in the search activity, but we should also have at least one stupid test to make sure the search activity actually works. Bonus points if we change the default search engine in Gecko and check to make sure that the search activity finds the right plugin. nalexander, can you help figure out how we can even go about making a test for this separate activity? Ideally we should be able to run this on automation.
Flags: needinfo?(nalexander)
Comment 1•10 years ago
|
||
This one might be best as a JUnit 3 test, which is currently soft blocked on https://bugzilla.mozilla.org/show_bug.cgi?id=1093218. Then you can use robotium (or any other framework) to UI test, but start a different activity. However, it might be that we can use the Robocop framework and just not rely on any of Robocop per se. (Under the hood, a Robocop test is a JUnit 3 test.) We might be able to just add a SearchActivityTest that is an ActivityInstrumentationTestCase2<Activity>, where the Activity is the SearchActivity, just like we do for Fennec (Gecko) Robocop tests. See [1]. [1] http://dxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/BaseRobocopTest.java#28
Flags: needinfo?(nalexander)
Comment 2•7 years ago
|
||
This is an ex-Search Activity now (bug 1221344).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•