Automated Test Coverage

From MozillaWiki
Revision as of 18:40, 30 December 2015 by Juliemccracken (talk | contribs) (→‎Program Status: Updated status)
Jump to navigation Jump to search
Fxossmall.png

Project Description

Enter text here

Requirements:

Enter text here

User Stories and Acceptance Criteria

Title BUG ID User story Acceptance Criteria
Removal of python from the Marionette harness Bug ID User Story 1 TBD Acceptance Criteria 1 TBD
Bug ID User Story 2 TBD Acceptance Criteria 2 TBD
Integration of Marionette test suite with Raptor Bug ID Real Bug # and User Story pending sync up with Eli Acceptance Criteria pending
Device testing on TaskCluster / Treeherder with Bitbar Bug ID User Story 1 TBD Acceptance Criteria 1 TBD
Bug ID User Story 2 TBD Acceptance Criteria 2 TBD

Automated Test Coverage

Milestone Due Date Status Notes
Convert integration tests from GIP to GIJ 12/31/15 AT RISK All but 14 have been converted. Engineers out on PTO.
Intermittently failing tests fixed 01/31/15 CHALLENGED Engineers are disabling the tests that fail intermittently and will fix them before re-enabling. Need more engineering help with this.
Tests that work on mulet work on device 01/31/15 CHALLENGED It's being reported that some of the flagged tests actually work on device. Need to reassess all.
Test Matrix created that defines platform(s) the tests are going to run on 12/31/15 AT RISK Draft of matrix completed but there are still some tests that need to be evaluated for appropriate testing environment. Won't get this done until January.
Automation of tests according to Test Matrix 05/31/16 ON TARGET Draft of matrix completed but there are still some tests that need to be evaluated for appropriate testing environment. Won't get this done until January.
Every single commit in gecko/gaia triggers automated tests 05/31/16 ON TARGET There's still work that needs to be identified and scheduled.
MozTrap scenarios automated using GIJ when feasible 05/31/16 ON TARGET
Working Mulet tests actively maintained with reporting on Treeherder 05/31/16 ON TARGET
Code Coverage Tool developed 12/31/15 AT RISK Originally targeted for end of Q4, but assistance at Mozlando didn't happen.

Status Key

Color Status Key
On Target The project or deliverable is expected to meet its due date.
Challenged The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track.
At Risk or Late The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late.
Done The project or deliverable has been completed.
On Hold The project or deliverable has been placed on hold.

Program Timeline

Release Timeline.png


MVP Scope

Querying by 2.6+ features

(please add correct bug tracking number)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);



Dependency Tracking

Dependency Gantt Chart.png


Detailed Program Plan

Action Item Engineering Owner QA Owner UX Owner Bugzilla ID Planned Done Actual Done

Program Stakeholders

Role Name IRC
EPM
EM
PM
TL
UX
QA
  • EPM = Engineering Program Manager
  • EM = Engineering Manager
  • PM = Product Manager
  • TL = Tech Lead
  • UX = User Experience
  • QA = Quality Assurance

UX Specs


Reference Links