tl;dr: When you mark a bug FIXED in Bugzilla, please set the
in-testsuite flag (preferably to "+" because you added tests)!
The test improvement team had its first meeting today, and one of our
goals was making it easier to track whether a bug has automated tests in
the test suite. Luckily for us, Bugzilla already has a flag to track
this: "in-testsuite".
When landing a patch, please always make sure to set the in-testsuite
flag. This flag can be found by looking at "Flags" on the right column
of the bug header and clicking "set flags".
If you have tests, just set in-testsuite to "+", and you're done! You
can also set in-testsuite to "+" if existing tests already cover the
patch (e.g. if you're just refactoring code).
If you don't have tests, but the patch should have tests, set
in-testsuite to "?" and file a followup to track landing the tests. When
they land, set in-testsuite to "+" for both bugs.
If tests just aren't necessary (e.g. for a CSS change), set in-testsuite
to "-" and provide a brief explanation of why.
Module owners/peers can also feel free to set in-testsuite to "?" on an
open bug to indicate that any patch for the bug should come with tests.
In general, *all* newly-FIXED bugs should have the in-testsuite flag set
to some value. The goal here is to provide an easy way for module
owners, managers, product folks, partners, etc to track the overall
testfulness of our work and to ensure that we're taking proactive steps
to prevent regressions.
If anyone has suggestions for how to improve this, just let me know.
I'll be adding this info to the wiki sometime in the next few days.
- Jim
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
