QA/Automation: Difference between revisions
(No more meetings) |
|||
| (23 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
= Summary = | = Summary = | ||
To offer the best quality of a software product like Firefox, test automation is a crucial part to lower the amount of time until a feature can be finally shipped, or QA can ensure that no major regressions are included in the upcoming next release of Firefox. Therefore our team is working closely together with the [[QA/Desktop_Firefox|Desktop Firefox]] team in selecting next major areas of work and analyzing the requirements for requested tests. | |||
To fulfill all of the requests we are heavily depending on our community. Nearly everyone of us is acting as a mentor and is happy to teach interested people to strengthen their knowledge in automation. If you are interested please join us via any of the contact links as shown below. | |||
= Contact = | |||
If you have questions stop by and talk to us in the [irc://irc.mozilla.org/#automation #automation IRC channel] ([http://logs.glob.uno/?c=automation logs from channel]) or by subscribing to our [https://lists.mozilla.org/listinfo/dev-automation automation mailing list] or [http://groups.google.com/group/mozilla.dev.automation newsgroup]. | |||
= Team = | = Team = | ||
{{:QA/Automation/Team}} | |||
{{:QA/Automation/ | |||
= | = Meetings / Events = | ||
We had public team meetings each and every Monday. Former meeting notes can be found on the [[/Meetings|meetings page]]. | |||
= Goals = | |||
{{:QA/Automation/Goals}} | |||
= | = Projects = | ||
{{:QA/Automation/Projects}} | |||
== | = Contribution = | ||
{{:QA/Automation/Contribution}} | |||
Latest revision as of 13:26, 8 August 2015
Summary
To offer the best quality of a software product like Firefox, test automation is a crucial part to lower the amount of time until a feature can be finally shipped, or QA can ensure that no major regressions are included in the upcoming next release of Firefox. Therefore our team is working closely together with the Desktop Firefox team in selecting next major areas of work and analyzing the requirements for requested tests.
To fulfill all of the requests we are heavily depending on our community. Nearly everyone of us is acting as a mentor and is happy to teach interested people to strengthen their knowledge in automation. If you are interested please join us via any of the contact links as shown below.
Contact
If you have questions stop by and talk to us in the #automation IRC channel (logs from channel) or by subscribing to our automation mailing list or newsgroup.
Team
The Firefox Automation team is a group of passionate and open minded people working on automation for Firefox. We are spread around the world, but we have one collective goal to empower automation even more in the Mozilla project. If you want to get in contact with one of us please check the table below for more information.
The Core Team
| Name | IRC nickname | Project Assignments |
| Henrik Skupin | :whimboo | Everything related to test automation for Firefox Desktop |
| Maja Frydrychowicz | :maja_zf | |
| Syd Polk | :spolk |
Contributors
| Name | IRC nickname | Interests |
| Szabolcs Hubai | :xabolcs | likes Nightly Tester Tools and Memchaser; knows JavaScript, want to know Python |
| Sandeep Murthy | N/A | likes Python, Marionette and automation tools |
Meetings / Events
We had public team meetings each and every Monday. Former meeting notes can be found on the meetings page.
Goals
Q3 2015
- Replace custom test runner script for firefox-ui-tests with mozharness when executing tests via Jenkins (1192369)
- Improve overall stability and result reporting to treeherder
- Standardized execution of tests for an easy change of the execution platform (e.g. taskcluster)
- Investigate requirements for running firefox-ui-tests via taskcluster instead of Jenkins (1192371)
- Joined work with taskcluster team to define requirements
- Create roadmap for taskcluster integration
Stretched Goals
- mozdownload has to download builds from AWS via taskcluster (278)
- Developer documentation for Firefox UI Tests
Goals Proposals
If you have ideas and want to propose those as a goal for our team for the next quarters, please go to our goals collection etherpad and enter them all together with your name.
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!
Firefox UI Tests
| Project | Technologies | Description |
| Firefox UI Tests | Python, Javascript | |
| Dashboard | Javascript, HTML, CSS, AJAX, CouchDB | 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 |
| Automation Training | - | Provide automation training to larger community through 4 automation training events |
| 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 | Puppet | 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 |
| TPS | Javascript, Python | Testing and Profiling tool for Sync |
| MTBF | Javascript, Python, Bash | Stability testing tool |
Contribution
- You can get started with one of our first good bugs: http://www.joshmatthews.net/bugsahoy/?automation=1&unowned=1&simple=1
- When you have more experience pick one of those bugs: http://www.joshmatthews.net/bugsahoy/?automation=1&unowned=1
Mozmill Tests
- You can get started with one of our first good bugs: http://mzl.la/1ikbQKQ
- When you have more experience pick one of those bugs: http://mzl.la/1rrV1Vu
Mozmill
- You can get started with one of our first good bugs: http://mzl.la/1rqYvG4
- When you have more experience pick one of those bugs: http://mzl.la/1ijPe32
Tools
- memchaser: https://github.com/mozilla/memchaser/issues?labels=mentored&state=open
- mozdownload: https://github.com/mozilla/mozdownload/issues?labels=mentored&state=open
- mozmill-automation: https://github.com/mozilla/mozmill-automation/issues?labels=mentored&state=open
- mozmill-ci: https://github.com/mozilla/mozmill-ci/issues?labels=mentored&state=open
- mozmill-dashboard: https://github.com/mozilla/mozmill-dashboard/issues?labels=mentored&state=open
- mozmill-environment: https://github.com/mozilla/mozmill-environment/issues?labels=mentored&state=open
- nightly tester tools: https://github.com/mozilla/nightlytt/issues?labels=mentored&state=open