Closed
Bug 411750
Opened 17 years ago
Closed 17 years ago
migrate major update testgroup to Fx3 test run
Categories
(Webtools Graveyard :: Litmus, defect, P2)
Webtools Graveyard
Litmus
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jbecerra, Assigned: coop)
Details
We currently have a "1.5x - 2.0x Major Update" test group in the Firefox 2.0 catchall test run, and we need to have it cloned so we have a "2.0x - 3.0x Major Update" test group. This is in preparation for MU testing for Fx3.
Assignee | ||
Updated•17 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Comment 1•17 years ago
|
||
The testgroups/subgroups/testcases have been cloned and moved forward. Notes: new testgroup id: 88 new subgroup_ids: 881,882 new testcase ids: 5090->5115 The testcase steps/results have *NOT* been updated to refer to 2.0->3.0. The sort order for the testcases in the extended subgroup (#882) is not set properly, but this is how they appeared in the original group (#836) which is also unsorted. Both subgroups may need to have their component testcases sorted.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•