B2G/QA/Automation/UI/Strategy/Document End to end Automation: Difference between revisions
< B2G | QA | Automation | UI | Strategy
Jump to navigation
Jump to search
No edit summary |
|||
| Line 20: | Line 20: | ||
* Strategy [Geo] | * Strategy [Geo] | ||
* Process/ownership diagram of current process from build to results [ | * Process/ownership diagram of current process from build to results [Martijn] | ||
* Updated and corrected Python tutorial [ | * Updated and corrected Python tutorial [John] | ||
* Language-agnostic best practices document for automation [Geo] | * Language-agnostic best practices document for automation [Geo] | ||
* Criteria document for picking UAT tests to automate [ | * Criteria document for picking UAT tests to automate [Martijn] | ||
* Criteria document for picking CI tests to automate [ | * Criteria document for picking CI tests to automate [Johan] | ||
Q2: | Q2: | ||
Revision as of 18:52, 11 February 2015
Objective
Document what we do so that we can onboard community more easily and so that our process and work is transparent.
Challenges Addressed
- Automation systems and concerns are poorly documented
The Problem
We don't have enough visibility in what we do and why we do it. There is frequent misunderstanding of our processes, scope, and purpose. And onboarding community is difficult because we don't have hard documentation to point at.
The Solution
Document all the things.
Timeline
Q1:
- Strategy [Geo]
- Process/ownership diagram of current process from build to results [Martijn]
- Updated and corrected Python tutorial [John]
- Language-agnostic best practices document for automation [Geo]
- Criteria document for picking UAT tests to automate [Martijn]
- Criteria document for picking CI tests to automate [Johan]
Q2:
- Update process/ownership diagram of build to results in JS
- Update best practices for UAT automation in JS
- JavaScript UAT tutorial
Risks
We need to be careful to only document at a level of detail we can afford to maintain.