Closed
Bug 972624
Opened 10 years ago
Closed 6 years ago
Add tests to ensure each device configuration has the appropriate toolbar/menu buttons
Categories
(Firefox for Android Graveyard :: Testing, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mcomella, Unassigned, Mentored)
References
Details
(Whiteboard: [lang=java])
bug 972327 is a regression where tablets misplace the refresh button - let's not let it happen again! This could be set up as a part of the UITest framework, or as a separate bug. Depends on bug 944142 where the AppMenu was implemented.
Reporter | ||
Comment 1•10 years ago
|
||
To make this a little clearer, different device configurations have different toolbar configurations: * Phones have tabs button and menu button * Tablets have back/forward buttons, refresh, bookmark, tabs, and menu * Too lazy to check what 7" tabs have. :P This bug is to write a test that checks the visibility/enabled state on each of these items to ensure the toolbar is being displayed as expected. Though we avoid drawing over previously drawn Views, it may be worthwhile to see if Robotium/Android has a way to see if a View is *actually* visible (i.e. not drawn over) and, if so, use that. Here, or as a followup, it may be worthwhile to verify that the menu button also has the appropriate options (e.g. back on phones, does not contain back on tablets, etc.).
Summary: Add tests to ensure each device configuration has the appropriate app menu → Add tests to ensure each device configuration has the appropriate toolbar/menu buttons
Assignee | ||
Updated•10 years ago
|
Mentor: michael.l.comella
Whiteboard: [mentor=mcomella][lang=java] → [lang=java]
Reporter | ||
Updated•10 years ago
|
Mentor: vivekb.balakrishnan
Comment 2•6 years ago
|
||
Mass closing Firefox for Android :: Testing bugs with no progress in 2017. If this bug is important to you, please re-open.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•3 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
•