QA/Automation/Projects/Mozmill Automation/On Demand Test Framework: Difference between revisions
< QA | Automation | Projects | Mozmill Automation
Jump to navigation
Jump to search
| Line 69: | Line 69: | ||
|- valign="top" | |- valign="top" | ||
| [[/Config|Config]] | | [[/Config|Config]] | ||
| Standardized configuration document for describing a test run | | Standardized configuration document for describing a test run | ||
|- valign="top" | |- valign="top" | ||
| [[/Demand|Demand]] | | [[/Demand|Demand]] | ||
| User-facing interface for demanding a test run | | User-facing interface for demanding a one-time test run | ||
|- valign="top" | |- valign="top" | ||
| [[/Dashboard|Dashboard]] | | [[/Dashboard|Dashboard]] | ||
| Line 78: | Line 78: | ||
|- valign="top" | |- valign="top" | ||
| [[/Executor|Executor]] | | [[/Executor|Executor]] | ||
| Kicks off and | | Kicks off and centrally controls the test run | ||
|- valign="top" | |- valign="top" | ||
| [[/Provisioner|Provisioner]] | | [[/Provisioner|Provisioner]] | ||
| | | Locates or creates an appropriate machine for execution | ||
|- valign="top" | |- valign="top" | ||
| [[/Machine|Machine]] | | [[/Machine|Machine]] | ||
| Agent, etc. on target machines | | Agent, etc. on target machines for remote execution | ||
|} | |} | ||
Revision as of 22:25, 31 October 2011
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 |
| Config | Standardized configuration document for describing a test run |
| Demand | User-facing interface for demanding a one-time test run |
| Dashboard | User-facing interface for tracking run status |
| Executor | Kicks off and centrally controls the test run |
| Provisioner | Locates or creates an appropriate machine for execution |
| Machine | Agent, etc. on target machines for 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.