Community
Participate
Working Groups
It has been suggested it would be good to have a generic "bug query" on the test results summary page that users/pmc/project leads/adopters could use to see which tests have been disabled. For example, we often disable a test if it is always failing ... just so that is it not "noise" on the test summary page ... until there is time/people to fix the test (or, the code that causes the test to fail). For there to be feasible generic bug query, we would need a convention of using a standard (or, two) prefix for such bugs ... such as [disabled test] or [restore test] and then the query could look for bug that contained that prefix.
At 5/29 status meeting, it was decided not to have a query on test summary page, that it would be too hard to "be accurate" for a particular release (and, too much work for too little gain) ... but will leave this bug open in case we want to adopt a convention for our own use. One suggestion made during the call was to use the keyword 'consistency'. ?
(In reply to comment #1) > At 5/29 status meeting, it was decided not to have a query on test summary > page, that it would be too hard to "be accurate" for a particular release > (and, too much work for too little gain) ... but will leave this bug open in > case we want to adopt a convention for our own use. > > One suggestion made during the call was to use the keyword 'consistency'. ? -1 for that. We should not (ab)use a keyword for something else than it is defined for. In this case it says: "For bugs related to cross-platform consistency." I think the easiest would be to add a tag into the whiteboard filed. That way we can define tags per release while even keeping the bug open.
