TestEngineering/Web/Automation: Difference between revisions
< TestEngineering | Web
Jump to navigation
Jump to search
No edit summary |
|||
| Line 23: | Line 23: | ||
== Meeting Notes == | == Meeting Notes == | ||
The Web QA no longer have a regular meeting to discuss automation. You can either attend the [[QA/Execution/Web_Testing#Meetings|Web QA weekly meeting]], or the [[Auto-tools/Automation_Development/Meetings|Automation Development meeting]]. The meeting notes from past meetings are available | The Web QA no longer have a regular meeting to discuss automation. You can either attend the [[QA/Execution/Web_Testing#Meetings|Web QA weekly meeting]], or the [[Auto-tools/Automation_Development/Meetings|Automation Development meeting]]. The meeting notes from past meetings are available [[QA/Execution/Web_Testing/Automation/Archived_Meeting_Notes|here]]. | ||
== Test Days == | == Test Days == | ||
Revision as of 22:17, 16 January 2013
Automation Homepage
The Web QA Automation team builds automated tests to run against Mozilla websites to make sure they are working as expected.
Documentation
- Jenkins
- Build Notifications
- Repositories
- Git Mirrors
- Selenium Grid
- Virtual Environments
- Credentials
- Style Guide
- PEP8 Pre-Commit Hook
- Code Review Process
- UnittestZero
- Pip Requirements
Useful Resources
Meeting Notes
The Web QA no longer have a regular meeting to discuss automation. You can either attend the Web QA weekly meeting, or the Automation Development meeting. The meeting notes from past meetings are available here.
Test Days
AMO - (outdated section)
- Libraries for Page Object Model
- Config Files
- Shared Libraries (pre-POM)
- Troubleshooting AMO test runs
- Conventions in AMO Test Cases
All of the above are legacy, and should be used solely as reference - stephend