QA/Execution/Web Testing/Project for Automation: Difference between revisions

QA/Execution/Web Testing/Project for Automation (view source)

97 bytes added , 28 March 2013

Confirmed users

1,504

edits

@@ Line 33: / Line 33: @@
 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.
+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. You may confer with the QA person[s] assigned to your project. Referring to previous projects and tests often give a good starting point for beginning automation. See the Reference section below to get more information.
 * <strong>Project creation on GitHub:</strong> Mozilla Admins have this permission. If it is unclear who should be ask, request project submission from StephenD.