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

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

Revision as of 18:51, 22 March 2013

330 bytes added , 22 March 2013

→‎Eligibility:

Rbillings

Confirmed users

1,504

edits

@@ Line 6: / Line 6: @@
 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 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>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.
 <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 17: / Line 19: @@
 <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. 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.
+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. This will include whether or not the project is a good candidate for automation, and also a timeframe that we believe it could be done in.
 ==What next?==