QA/Triage: Difference between revisions

QA/Triage (view source)

26 bytes added , 19 September 2006

m

Confirmed users

162

edits

@@ Line 8: / Line 8: @@
 Mozilla is an amazing project. Bugs come in from just about
-anywhere -- end users,  developers and QA teams scattered
+anywhere -- end users,  developers, and QA teams scattered
 across many organizations. The great benefit is that the various
 products are extremely thoroughly tested on a day to day basis and
@@ Line 19: / Line 19: @@
 Unfortunately, even with all of this useful information, there is a
-lot of noise. The community often files invalid, duplicate, already
+lot of noise. The less experienced community members often file invalid, duplicate, already fixed, improperly filed, and relatively incomplete bugs.
-fixed, improperly filed and relatively incomplete bugs. That
+That said, community bugs are an invaluable source of information, as
-said, community bugs are an invaluable source of information, as
 the testing coverage would not be nearly as wide without it. In
 Mozilla, a QA must not only test and then file their own bugs, but
@@ Line 33: / Line 32: @@
 How does the QA community harness the flood of filed bugs into
 better quality for Mozilla while maximizing productivity for
-developers? Let's take a look ... there's <i>a lot</i> you can do without coding.
+developers? Let's take a look... there's <i>a lot</i> you can do without coding.
 == How to Track Relevant Incoming Bugs ==