Confirmed users
1,247
edits
No edit summary |
|||
| Line 53: | Line 53: | ||
If you see an issue which is new to you, please follow these steps to make sure the QA team can act on it, if its a valid bug. | If you see an issue which is new to you, please follow these steps to make sure the QA team can act on it, if its a valid bug. | ||
* Gather the following details about each issue (you can use [http://etherpad.mozilla.com:9000/beta-investigations this etherpad] to help track the issues and share details with the rest of the team): | |||
** Links to forum threads | |||
** Firefox version(s) affected? Which operating systems? | |||
** Which add-ons? | |||
** Affected site(s) | |||
** Related bugs from searching Bugzilla | |||
** Importance | |||
** How often does it happen? | |||
** Potential workarounds? | |||
** Does this prevent users from using the browser? | |||
* See if you can reproduce the bug on your own computer. Ask someone else on the team if you don't have the necessary hard or software. | * See if you can reproduce the bug on your own computer. Ask someone else on the team if you don't have the necessary hard or software. | ||
* If you can't find related bugs for an issue and you can reproduce it, file a new bug with steps to reproduce and all the relevant details. Please ping Cww, zzxc and Topal on IRC when you do this so we know. | |||
** Note: if you are filing a security bug, please ping Cww in private. | |||
===Doing further QA work=== | |||
As we figure out details the major issues, there may be followup QA work, if you'd like to get involved in any of these following steps, just offer! We'll be updating the etherpad with followup things that need doing. If you need help with these steps, just ask in #sumo or #qa. | |||
* Finding a regression range | |||
* Testing builds | |||
* Building a reduced test case | |||
== Next meeting == | == Next meeting == | ||
10am PDT in #sumoMtg (1pm Eastern Daylight Time, 7pm CEST). | 10am PDT in #sumoMtg (1pm Eastern Daylight Time, 7pm CEST). | ||