Confirmed users
9,511
edits
QA/Execution/Web Testing/Project for Automation: Difference between revisions
QA/Execution/Web Testing/Project for Automation (view source)
Revision as of 19:22, 18 March 2013
, 18 March 2013→Eligibility:
No edit summary |
|||
| Line 6: | Line 6: | ||
While the prospect of automation often sounds like it'd improve any project, unfortunately that is not possible to do. The bottom line is that there needs to be a vetting process as the team does not have the resources to automate every project. There are qualities which make a project a better candidate for automation. | While the prospect of automation often sounds like it'd improve any project, unfortunately that is not possible to do. The bottom line is that there needs to be a vetting process as the team does not have the resources to automate every project. There are qualities which make a project a better candidate for automation. | ||
Urgency: What is the urgency of your project? This includes whether it's a high priority for the company or if it has a short deadline. Both of these need to be considered. | <strong>Urgency: What is the urgency of your project? This includes whether it's a high priority for the company or if it has a short deadline. Both of these need to be considered. | ||
Lifespan: Is your project permanent? Is it going to be a maintained project that will last a year or more? Or is this a short term project? The lifespan of a project does impact the eligibility of it for automation. | Lifespan: Is your project permanent? Is it going to be a maintained project that will last a year or more? Or is this a short term project? The lifespan of a project does impact the eligibility of it for automation. | ||