QA/Mozmill Test Automation/Dashboard/Roadmap/0.4: Difference between revisions
< QA | Mozmill Test Automation | Dashboard | Roadmap
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
==Functionality== | ==Functionality== | ||
Front End | |||
* Filter by: | * Filter by: | ||
** Locale | ** Locale | ||
| Line 8: | Line 9: | ||
** Build/Version (Ideally select a range) | ** Build/Version (Ideally select a range) | ||
** Date | ** Date | ||
*Tag Bugs | |||
* | |||
* Linking test modules to the repository for easier investigation of failures | * Linking test modules to the repository for easier investigation of failures | ||
Application Server | |||
*Deal with users | |||
**Ideally through LDAP so we don't have to roll a registration system | |||
*Tag Bugs | *Tag Bugs | ||
** Add/Change/Remove of bug numbers to specific failures | ** Add/Change/Remove of bug numbers to specific failures | ||
** Add Comments | ** Add Comments | ||
* | Elastic Search | ||
*Connect River to backend storage | |||
* | Backend Storage | ||
** | * Map-Reduce Reports | ||
** failures/passes per function | |||
** Probably will require a different db/index | |||
==Tasks== | ==Tasks== | ||
Revision as of 21:52, 16 May 2011
Version 0.4
With version 0.4 we are planning to replace the CouchDB backend of the Dashboard with probably ElasticSearch. Therefore more time is necessary, so we do not expect to see the release before end of Q2 in 2011. Owen Coutts will mainly work on that release during his internship.
Functionality
Front End
- Filter by:
- Locale
- OS
- Build/Version (Ideally select a range)
- Date
- Tag Bugs
- Linking test modules to the repository for easier investigation of failures
Application Server
- Deal with users
- Ideally through LDAP so we don't have to roll a registration system
- Tag Bugs
- Add/Change/Remove of bug numbers to specific failures
- Add Comments
Elastic Search
- Connect River to backend storage
Backend Storage
- Map-Reduce Reports
- failures/passes per function
- Probably will require a different db/index
Tasks
- Q1
- Define specs and requirements for the replacement dashboard
- Create an Elastic Search pilot application to confirm the expected functionality
- Q2
- Update specs and requirements based on pilot application
- Implement features based on specs in multiple milestones
- Deploy application to production
- Hold a brownbag to present the new dashboard
Progress
- Prototype
- Proof of concept to show that at least the same functionality can be rolled with elastic search.
- Technical Knowledge learned can be found here: Proof of Concept Prototype