Closed Bug 850632 Opened 12 years ago Closed 8 years ago

Annotate failing reftest tests

Categories

(Firefox for Metro Graveyard :: Tests, defect, P5)

Product:
Firefox for Metro Graveyard
Component:
Tests
Platform:
All
Windows 8.1
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: jimm, Unassigned)

References

Details

(Whiteboard: p=0)

+++ This bug was initially created as a clone of Bug #843420 +++ Once bugs like bug 837772 and bug 837772 are fixed, Metro Firefox will be able to run test suites that are shared with desktop Firefox and other Mozilla applications. Some of these tests will fail because of bugs or missing features in Metro Firefox; others will fail because of bad assumptions in the test code. We will need to record all tests that are failing, and provide ways to skip the tests or ignore the failures until they are fixed, similar to the mechanisms we already use for this on other apps/platforms. For mochitests we can create a "metro.json" file in /testing/mochitest similar to android.json and b2g.json. For xpcshell and reftest-style tests, we can add new annotations to the existing manifest files (xpcshell.ini, reftest.list, crashtest.list, etc.).
Summary: Annotate failing mochitest tests → Annotate failing reftest tests
Whiteboard: feature=work
Whiteboard: feature=work → [shovel-ready] feature=work
strawman: priority 2 why: iirc, we need this to be build tier 1, which is something we will want to be once we move closer to release.
Priority: -- → P2
Summary: Annotate failing reftest tests → Work - Annotate failing reftest tests
Blocks: metrobacklog
Summary: Work - Annotate failing reftest tests → Annotate failing reftest tests
Whiteboard: [shovel-ready] feature=work → [feature] p=0
Priority: P2 → --
Priority: -- → P5
Whiteboard: [feature] p=0 → p=0
OS: Windows 8 Metro → Windows 8.1
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.