QA/Automation/Projects: Difference between revisions

From MozillaWiki
< QA‎ | Automation
Jump to navigation Jump to search
Line 6: Line 6:


=== Prioritized Projects ===
=== Prioritized Projects ===
Each quarter the [https://wiki.mozilla.org/QA Mozilla QA team] has some [https://wiki.mozilla.org/QA/Goals/Q4 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.
{| class="fullwidth-table sortable"
 
|-
For 2013 Q4 our prioritized projects are:
| style="background:#EFEFEF; width:25%" | '''Project'''
* {{done|}}(crossteam) Get SoftVision to lead the automation efforts for QA with our oversight
| style="background:#EFEFEF; width:18%" | '''Technologies'''
* {{done|}}(crossteam) Switch Mozmill CI from Mozmill 1.5.x to Mozmill 2.0 (see [https://github.com/mozilla/mozmill-ci/issues/329 issue 329])
| style="background:#EFEFEF; width:57%" | '''Description'''
* {{miss|}}(crossteam) Get Firefox Metro tests executed in production (see [https://github.com/mozilla/mozmill-ci/issues/215 issue 215])
|- valign="top"
* {{done|}}(crossteam) AWSY Firefox OS Memory Tests ({{bug|899194}})
| [[QA/Automation/Projects/Mozmill_Automation/Puppet|Puppetizing Mozmill CI]]
* {{miss|}}Extend Mozmill CI to cover most of our localized beta and release candidate builds (see [https://github.com/mozilla/mozmill-ci/issues/270 issue 270])
| Shell, Puppet
* {{done|}}Create web application to generate the beta and release Jenkins job configuations (see [https://bugzilla.mozilla.org/show_bug.cgi?id=915164 bug 915164])
| Ensure Mozmill systems are controlled by puppet for updates on all Linux (bug 973535) and Mac (bug 996629) nodes
* {{done|}}Deploy automated Eideticker system to run nightly for Firefox OS (see {{bug|904837}})
|- valign="top"
 
| [[QA/Automation/Projects/TPS|TPS]]
Beside those we also have goals which are stretched and we might work on if there is time left:
| Python, Jenkins
* Setup tryserver Mozmill CI system assist team members in testing their patches
| Set up TPS (sync automation) continuous integration
* Investigate requirements for community driving tool by working together with jdm, lizzard, and pieros
|- valign="top"
| [[QA/Automation/Projects/Test_Creation|Creation of Tests]]
| Javascript
| Automate specific tests as identified by Desktop team
|- valign="top"
| [[QA/Automation/Projects/Automation_Training|Automation Training]]
| -
| Provide automation training to larger community through 4 automation training events
|- valign="top"
| [[QA/Automation/Projects/Mozmill|Mozmill]]
| Javascript, Python
| Replace the local httpd.js web server of Mozmill with mozhttpd to have it using marionette as its engine in the future
|}


=== All Projects ===
=== All Projects ===

Revision as of 06:57, 30 April 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

Project Technologies Description
Puppetizing Mozmill CI Shell, Puppet Ensure Mozmill systems are controlled by puppet for updates on all Linux (bug 973535) and Mac (bug 996629) nodes
TPS Python, Jenkins Set up TPS (sync automation) continuous integration
Creation of Tests Javascript Automate specific tests as identified by Desktop team
Automation Training - Provide automation training to larger community through 4 automation training events
Mozmill Javascript, Python Replace the local httpd.js web server of Mozmill with mozhttpd to have it using marionette as its engine in the future

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