Closed Bug 1252961 Opened 8 years ago Closed 8 years ago

Investigate robocop test situation after disabling GB

Categories

(Firefox for Android Graveyard :: Testing, defect)

Product:
Firefox for Android Graveyard
Component:
Testing
Platform:
All
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox48 fixed, fennec48+)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox48 --- fixed
fennec 48+ ---

People

(Reporter: mcomella, Assigned: gbrown)

References

Details

There are some tests that only run on GB so when we disable GB, the tests won't run anymore. Find out if they're important and if so, let's get them working on the newer versions!
Going through robocop.ini, here's a list of tests disabled on API 18 but not API 10 (so only running on GB, afaik):

testAdobeFlash
testAxisLocking
testFlingCorrectness
testLinkContextMenu
testPanCorrectness
testPictureLinkContextMenu
testBrowserDiscovery
testHistoryService
testTrackingProtection
tracking-fennec: --- → ?
We should figure out if we're okay removing these tests, or what needs to happen to re-enable them on API 18.

gbrown, can you own this?
tracking-fennec: ? → 48+
Flags: needinfo?(gbrown)
Assignee: nobody → gbrown
Flags: needinfo?(gbrown)
Depends on: 1146420
Depends on: 1144874
Depends on: 1083666
Depends on: 1158384
Depends on: 1116036
Depends on: 1158363
Depends on: 1031496
testAdobeFlash remains disabled but all the other tests identified in Comment 1 have been enabled now. testAdobeFlash runs in autophone.
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox48: --- → fixed
Resolution: --- → FIXED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.