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:42, 29 March 2013
, 29 March 2013→Eligibility:
| Line 6: | Line 6: | ||
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. | 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. | |||
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. | **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? Permanent projects are more likely to get automated. | |||
<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. | |||
Is it going to be a maintained project that will last a year or more? Long term projects are better automation candidates. | *<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. | ||
*<strong>Coverage Complexity:</strong> Are you requesting to have a short smoke test automated, or in-depth coverage of a full product? How much needs to be done, and how quickly? These are important elements for automation. Team resources need to be scoped out, as far in advance as is possible. | |||
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>Discussion:</strong> The bottom line is that there cannot be any cut-and-dry formula to determine if a project is a good candidate for automation. There is a lot that depends on the project, its urgency, and the resources the team has available. Web QA wants to be available as a resource, however it's just not possible to always say 'Yes', which is why there is a need for discussion. Even if it is not possible to do right now, there is a possibility that eligibility may change in the future. For example we initially said no to marketing projects, however since then we have created a short template for those projects that actually carved off time for manual testing. So please talk to us! | ||
*<strong> Submission:</strong> Submitting your project to the Web QA team involves [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=stephen.donner%40gmail.com&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=&component=General&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-4=X&flag_type-41=X&flag_type-607=X&flag_type-791=X&flag_type-800=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Mac%20OS%20X&priority=--&product=Mozilla%20QA&qa_contact=&rep_platform=x86&requestee_type-325=&requestee_type-4=&requestee_type-41=&requestee_type-607=&requestee_type-781=&requestee_type-787=&requestee_type-791=&requestee_type-800=&short_desc=%5BAutomation%5D&status_whiteboard=&target_milestone=---&version=unspecified submitting a bug to Bugzilla.] | |||
<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. | |||
<strong>Coverage Complexity:</strong> Are you requesting to have a short smoke test automated, or in-depth coverage of a full product? How much needs to be done, and how quickly? These are important elements for automation. Team resources need to be scoped out, as far in advance as is possible. | |||
<strong>Discussion:</strong> The bottom line is that there cannot be any cut-and-dry formula to determine if a project is a good candidate for automation. There is a lot that depends on the project, its urgency, and the resources the team has available. Web QA wants to be available as a resource, however it's just not possible to always say 'Yes', which is why there is a need for discussion. Even if it is not possible to do right now, there is a possibility that eligibility may change in the future. For example we initially said no to marketing projects, however since then we have created a short template for those projects that actually carved off time for manual testing. So please talk to us! | |||
<strong> Submission:</strong> Submitting your project to the | |||
Let us know the scope of your project, and the timeline. The more information we have, the easier it is to work with your project. Also, the sooner you let us know a project will need Automation the better. | Let us know the scope of your project, and the timeline. The more information we have, the easier it is to work with your project. Also, the sooner you let us know a project will need Automation the better. | ||