QA Tips

Send useful bug/task feedback

The DB is where most of the time is spent:

• logging new issues
• answering questions from other developers
• regressing bugs

Keeping a clean DB is very useful; add extra info that isn't required but is useful for testers

• how a bug was fixed
• which build the fix will be included in

Test locally before submitting a blind fix

Have a tester try to reproduce the bug at your workstation

• This cuts back on the number of bugs bumped back to devs
• Directly ask for help understanding a bug/task, it's faster than submitting a bug/task with a question in comments

###Think of QA when adding features

• Do debug features help test them?
• Is the new feature ready for testing? (Yes - tell QA that there's a new feature to test in an upcoming build)
• Invite QA to stand-up meetings (keeps QA up-to-date with developemnts, current work, removed features, etc.)