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 17:32, 28 March 2013
, 28 March 2013→Eligibility:
| Line 4: | Line 4: | ||
==Eligibility:== | ==Eligibility:== | ||
Automation can be a great way to increase coverage for a project. If you have a project, this document will outline the process of submitting it for consideration. It is important to note that not all projects are candidates for automation. There are certain qualities of a project, outlined below, that increase the likelihood of QA implementing it. | |||
<strong>Urgency:</strong> What is the urgency of your project? If your project is a high priority for the company, or on the QA goals list, then it will be more likely to get automated. If it is a low priority, it may be some time before your project is eligible for automation. | <strong>Urgency:</strong> What is the urgency of your project? If your project is a high priority for the company, or on the QA goals list, then it will be more likely to get automated. If it is a low priority, it may be some time before your project is eligible for automation. | ||