Confirmed users
1,504
edits
QA/Execution/Web Testing/Project for Automation: Difference between revisions
QA/Execution/Web Testing/Project for Automation (view source)
Revision as of 21:51, 27 March 2013
, 27 March 2013→What next?
| Line 31: | Line 31: | ||
==What next?== | ==What next?== | ||
After your project has been nominated for automation, and resources have been scheduled these are the next steps | After your project has been nominated for automation, and resources have been scheduled these are the next steps towards automation. There is no set division of labor for these tasks, and we invite every project team to get involved. Specifically we invite devs to help set up and maintain jobs for their projects in our CI. This is an opportunity to work more closely with QA, and to help your own project along! | ||
We realize that these tasks may be new or unfamiliar to people outside of QA. Unfortunately we cannot provide exact set-up details as each project has unique needs and constraints. However, QA will be available to provide help. A list of similar projects and tasks to be used as a starting point has been included at the end of the page for reference. | |||
* <strong>Project creation on GitHub:</strong> Mozilla Admins have this permission. If it is unclear who should be ask, request project submission from StephenD. | * <strong>Project creation on GitHub:</strong> Mozilla Admins have this permission. If it is unclear who should be ask, request project submission from StephenD. | ||