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

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

220 bytes added , 22 March 2013

Confirmed users

1,504

edits

@@ Line 10: / Line 10: @@
 If there is a short deadline for an automation project, this reduces the chance of it being automated fully or on schedule. Ideally projects are submitted for automation with plenty of leeway for deadlines. If your project has a very short and tight deadline, it may not be a good candidate for automation.
-<strong>Lifespan:</strong> 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.
+<strong>Lifespan:</strong> Is your project permanent? Permanent projects are more likely to get automated.
+Is it going to be a maintained project that will last a year or more? Long term projects are better automation candidates.
+Or is this a short term project? Short term projects are not eliminated from automation, but the scope of what can or should be done is limited. The lifespan of a project does impact the eligibility of it for automation.
 <strong>UI Stability:</strong> Is the project in a stable phase, or is it new to development? More stable projects are better candidates for automation. A changing UI makes for a higher intensity of development to keep up with the evolution of the site. Revamping a site's UI may be a good time to create or edit automation also.