Confirmed users
9,511
edits
QA/Execution/Web Testing/Project for Automation: Difference between revisions
Jump to navigation
Jump to search
QA/Execution/Web Testing/Project for Automation (view source)
Revision as of 19:25, 18 March 2013
, 18 March 2013→What next?
| Line 19: | Line 19: | ||
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: | ||
* Project creation on | * <strong>Project creation on GitHub:</strong> Mozilla Admins have this permission. If it is unclear who should be ask, request project submission from StephenD. | ||
* Jenkins : Access is based on LDAP. Any team member can get access to view the Jenkins project dashboard. Currently Jenkins can be set to pull SCM (source code management), and given how many minutes for the interval. It is given the developer's GitHub repo and then goes to the dev site every 15-35 minutes to look for changes. Due to firewall issues, it is not possible at this time to do a pull when there is a change rather than a timed interval. | * <strong>Jenkins:</strong> Access is based on LDAP. Any team member can get access to view the Jenkins project dashboard. Currently Jenkins can be set to pull SCM (source code management), and given how many minutes for the interval. It is given the developer's GitHub repo and then goes to the dev site every 15-35 minutes to look for changes. Due to firewall issues, it is not possible at this time to do a pull when there is a change rather than a timed interval. | ||
* Test creation: Project requirements, including test coverage requests will be discussed by the team. Resources will be based on availability and need. | * <strong>Test creation:</strong> Project requirements, including test coverage requests will be discussed by the team. Resources will be based on availability and need. | ||
* Test maintenance: Test maintenance can be done by QA or team members. This can be determined on a per-project basis. | * <strong>Test maintenance:</strong> Test maintenance can be done by QA or team members. This can be determined on a per-project basis. | ||
* IRC notifications: IRC can be set up to notify the project team in any channel when the project status changes. For example, if it's been failing and suddenly passes it will generate a notification. Alternately it will notify the channel if tests which have been passing suddenly fail. You can check the status of any project by this IRC command, "qatestbot: status name.of.job [ex: qmo.prod]" | * <strong>IRC notifications:</strong> IRC can be set up to notify the project team in any channel when the project status changes. For example, if it's been failing and suddenly passes it will generate a notification. Alternately it will notify the channel if tests which have been passing suddenly fail. You can check the status of any project by this IRC command, "qatestbot: status name.of.job [ex: qmo.prod]" | ||