QA/Automation/Projects/Mozmill Automation/On Demand Test Framework
< QA | Automation | Projects | Mozmill Automation
Jump to navigation
Jump to search
Overview
TBD
| Name: | On-Demand Test Framework |
| Leads: | Geo Mealer, Henrik Skupin |
| Contributors: | TBD |
| Tracker: | TBD |
| QA Tracking Page: | TBD |
| Etherpad: | TBD |
Goals for Q4/11
TBD
| Status | Task | Description |
| Not started | Subgoal 1 | Description |
| Not Started | Subgoal 2 | Description |
Project Milestones
TBD
| Status | Milestone | Description |
| Not started | Milestone 1 | Description |
| Not Started | Milestone 2 | Description |
Modules/Interfaces
Note that the CI Trigger/Configuration Generator are a proposed part of the CI goal for this system, and will not be documented here.
| Component | Description |
| Demand | User-facing interface for demanding a test run |
| Config | Standardized configuration document for describing a test run |
| Dashboard | User-facing interface for tracking run status |
| Executor | Module that kicks off and broadly controls the test run |
| Machine Provisioner | Module that distributes test demands to machines as appropriate. Will eventually be responsible for rolling back/starting VMs as needed. |
| Test Machine | Whatever is necessary on target machines to allow remote execution |
In addition to these, Status formats must be defined where they exist in the architecture. It is unknown yet as to which module will define these, or whether they will be significant enough to require subprojects.