303614 - add testcase flags to more products in mozilla.org's bugzilla instance

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Bob Clary [:bc] (inactive)]

Back in April, we added a testcase flag to the JavaScript Engine Component. I
have found it extremely useful in managing the work flow of triaging bugs for
test cases to be added to the JavaScript Test Library and would like to expand
its use to other Products/Components as well.

I think the following Products should have the new testcase flag added:

Core
Firefox
Mozilla Application Suite
Thunderbird
Toolkit
Update

Candidates for other inclusions?

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

In case these are per-component, I think it'd be nice having this flag in the
networking components

Comment 2

[timeless]

i'd expect that nspr/nss would use this flag if given the chance. i've added it 
to everyone listed except update, plus i added it to rhino.

i'd like someone from update to speak up, at the very least indicating they 
could use it. by someone, i mean someone in authority.

Comment 3

[Wan-Teh Chang]

Is "testcase" a keyword?  I don't understand what you mean
by "testcase flags".

Comment 4

[timeless]

a flag is like a keyword, except instead of sharing space with all the other 
keywords, it burns space to the right of the keywords field, eventually 
elongating the table containing qa contact..keywords. on this page for unknown 
reasons we have keywords for "blocking-aviary1.0.7", "blocking-aviary1.5", 
and "blocking-aviary2.0". please look soon because i intend to kill those evil 
flags as they have no business in this product.

Comment 5

[Asa Dotzler [:asa]]

flags are different than keywords in that they can easily represent a request
and a request fulfillment. A testcase flag is added to a product (or component)
so that people working with bugs in that area can request that a testcase be
made and so that when that testcase is completed, the flag can make that clear. 

Comment 6

[Michael Morgan [:morgamic]]

(In reply to comment #2)
> i'd like someone from update to speak up, at the very least indicating they 
> could use it. by someone, i mean someone in authority.
We could definitely use this to help prevent pushing improperly tested updates
into production.  It's a great idea.  Mike Connor or Rafael Ebron might have
more input on this, but it's fine with me.

Comment 7

[timeless]

for reference (since only a limited number of blessed people can see) the 
description:
Whether the bug has a testcase in the test suite or not. Set it to "testcase?" 
if the bug needs a testcase (only set this if the bug actually <em>needs</em> a 
testcase &mdash; not all bugs do, even layout bugs!), set it to "testcase+" if 
the bug has an appropriate testcase, and set it to "testcase-" if the bug 
doesn't need an explicit testcase (e.g. for code cleanup bugs). Only QA 
actively working on test cases in the component should use this keyword.

--
it sounds like you could use a "tested" flag, which should not be confused with 
a "testcase" flag. if you'd like a "tested" flag, you can file a bug in this 
component and someone will add it. if i'm mistaken and you really think you 
have a use for testcase, please correct me.

Comment 8

[Asa Dotzler [:asa]]

I think that we already cover "tested" with the status VERIFIED.

Comment 9

[Nick Bebout]

*** Bug 181283 has been marked as a duplicate of this bug. ***

Comment 10

[Gervase Markham [:gerv]]

We now have the in-testsuite flag, which has a ? status for requesting a testcase, and it's in a great number of products.

Gerv