Confirmed users
4,378
edits
| Line 9: | Line 9: | ||
== Tips and Tricks: == | == Tips and Tricks: == | ||
* [http://www.youtube.com/watch?v=14W-XguG--U Quick Searching by typing in firefox URL] | * [http://www.youtube.com/watch?v=14W-XguG--U Quick Searching by typing in firefox URL] | ||
= Before Filing = | |||
== Check for Dups == | |||
* Verify that there isn't a bug on it first | |||
** Sometimes searching for the bug isn't easy. There's many ways to say what a bug is or how a bug is affected. Getting used to some of the terminology helps out greatly. | |||
== Know your audience == | |||
* who is your audience? | |||
# developers : Make it easy for the developers to understand how to reproduce the bug; they are the ones fixing the bug you find! | |||
# other qa : Make it easy for the other QA to reproduce your issue to verify if it's fixed or not | |||
# PMs/EPMs/Releng Managers : They need to understand how critical the bug is to place fixing the bug in the schedule | |||
= Creating a bug = | = Creating a bug = | ||