QA/Automation/Projects/Mozmill Automation/On Demand Test Framework
< QA | Automation | Projects | Mozmill Automation
Overview
TBD
| Name: | On-Demand Test Framework |
| Leads: | Geo Mealer, Henrik Skupin |
| Contributors: | TBD |
| Tracker: | TBD |
Goal History
| Period | Status | Goal |
| 2011 Q4 | [ON TRACK] | Implementation of a remote mechanism to trigger Mozmill functional and update tests for Firefox releases |
Project Milestones
| Status | Milestone | Description |
| Design Stage [ON TRACK] | Basic Execution | System allows execution of test-run demands against standing machines. |
| Not started | Auto-Provisioning | System automatically provisions and/or resets virtual machines |
| Not started | Parallelism | System knows how to slice up a test run more finely than per-platform |
Architecture
The Trigger and Config Generator components are a proposed part of integrating the CI goal into this system by automatically generating a Demand, and will not be covered in this project.
| Component | Description |
| Demand | User-facing interface for demanding a one-time test run |
| Config | Standardized configuration document for describing a test run |
| Dashboard | User-facing interface for tracking run status |
| Executor | Kicks off and centrally monitors the test run |
| Provisioner | Initializes appropriate machines for execution |
| Machine | Environment on target machines for remote execution |
If an off-the-shelf CI tool like Jenkins turns out be appropriate for our needs, it may subsume the Dashboard and Executor components.
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.