Closed Bug 997502 Opened 11 years ago Closed 5 years ago

Implement test coverage to ensure Yahoo codes don't regress

Categories

(Firefox for Android Graveyard :: General, defect)

27 Branch
All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mconnor, Unassigned)

References

Details

This was an issue in bug 983723, but lack of automated testing meant bug 997402 happened without test failures. Let's make sure this never happens again. Test plan for Yahoo: Engine is present and enabled. Engine has a valid text/html URL Engine has a suggestions URL with the following properties: appid=ffm output=fxjson command=<search term> All searches must have the following parts: p=<search term> ei="UTF-8" fr=mozilla_mobile_search If we can test that we get results/suggestions, so much the better, but these URLs should be pretty stable.
Note for posterity: fr != mozilla_mobile_search. See Bug 1033000.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.