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 18:45, 22 March 2013

937 bytes added ,  22 March 2013
→‎Eligibility:
Line 4: Line 4:


==Eligibility:==
==Eligibility:==
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.
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? 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:</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 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.


<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? 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.  
Line 16: Line 16:
<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>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 WebQA team involves submitting a bug to Bugzilla.
<strong> Submission:</strong> Submitting your project to the WebQA 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.]
Let us know the scope of your project, and the timeline. Contacting us is as easy as emailing the QA person you know on the team, or the manager Stephen Donner [sdonner@mozilla.org]. After contacting us, we will review the project. We will incorporate all of the considerations listed above and let you know the status.
= 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.
= After contacting us, we will review the project. We will incorporate all of the considerations listed above and let you know the status as soon as possible, within 3 working days.


==What next?==
==What next?==
Rbillings
Confirmed users
1,504

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/640757"

Navigation menu