QA/Automation/Projects: Difference between revisions
No edit summary |
|||
| Line 53: | Line 53: | ||
| Javascript | | Javascript | ||
| Building and enhancing the API and shared modules for our Mozmill tests for Firefox | | Building and enhancing the API and shared modules for our Mozmill tests for Firefox | ||
|} | |} | ||
Revision as of 14:52, 13 January 2014
Projects
Some of our projects can be accomplished in a short time while others will take longer, even several months. The prioritized projects reflect the most important projects in the current quarter and include the appropriate tasks which have to be fulfilled during that time. Other active projects have lower priority.
If you are interested in already finished projects, check our projects archive. We also have a some projects that we would like to do in the future!
Prioritized Projects
Each quarter the Mozilla QA team has some goals to finish, and some of those are dedicated to our team. That means we have some prioritized projects to handle throughout the current quarter, which have higher priority then other listed projects on that page.
For 2013 Q4 our prioritized projects are:
- [DONE] (crossteam) Get SoftVision to lead the automation efforts for QA with our oversight
- [DONE] (crossteam) Switch Mozmill CI from Mozmill 1.5.x to Mozmill 2.0 (see issue 329)
- [MISSED] (crossteam) Get Firefox Metro tests executed in production (see issue 215)
- [DONE] (crossteam) AWSY Firefox OS Memory Tests (bug 899194)
- [MISSED] Extend Mozmill CI to cover most of our localized beta and release candidate builds (see issue 270)
- [DONE] Create web application to generate the beta and release Jenkins job configuations (see bug 915164)
- [DONE] Deploy automated Eideticker system to run nightly for Firefox OS (see bug 904837)
Beside those we also have goals which are stretched and we might work on if there is time left:
- Setup tryserver Mozmill CI system assist team members in testing their patches
- Investigate requirements for community driving tool by working together with jdm, lizzard, and pieros
All Projects
Mochitests
| Project | Technologies | Description |
| WebRTC | Javascript, HTML | Creation of a testsuite to qualify stability of WebRTC |
Mozmill
| Project | Technologies | Description |
| Automation | Python, Jenkins | Scripts and Tools to enhance the automation for Mozmill related testing |
| Dashboard | Javascript, HTML, CSS, AJAX, CouchDB, ElasticSearch | Dashboard to visualize Mozmill test results from the automated test-runs and the Mozmill Crowd extension |
| Shared Modules | Javascript | Building and enhancing the API and shared modules for our Mozmill tests for Firefox |
Other Projects
| Project | Technologies | Description |
| Add-ons | CSS, Javascript, XML | To help any team in the Mozilla project we work on several extensions. |
| Documentation | Wiki | Establish the team presence across websites (Wiki, MDN) and improve the documentation to increase collaboration with the test automation community |
| Infrastructure | ESX, VMware | Building up and maintaining the infrastructure for automation tasks |
| Open Web Applications | Javascript, Python | Implemention of necessary APIs and support the addition of tests to execute automated tests for web apps in Firefox |
| GaiaUI Endurance Tests | Gaiatest, Python, Javascript, Datazilla | Implemention and maintenance of on-device gaia endurance tests to search for Firefox OS memory regressions |
| Games Benchmarking | Gaiatest, Python, Javascript | Add support for performing standardized games benchmarking tests on the Firefox OS browser |