I feel that this issue is important enough to highlight as a separate
component. As you point out the test component has many items which
are not current nightly test failures - and there is no easy way to tell
which are.
I really want a way to highlight those problems that are causing test
failures for those looking to check into the code. As many have already
said this causes specific developer problems for subsequent checkins.
As you say many in the test category may really need to be changed to
improvements. But I could also imagine test bugs which actually don't
result in test failures (for instance in canon based tests, maybe
someone notices by inspection that master file has the wrong result for
a query).
Andrew McIntyre wrote:
On Jan 19, 2006, at 2:51 PM, Mike Matrigali wrote:
I like the idea of adding a new component to JIRA, and to encourage
anyone who sees a problem in test run to file an issue there.
I agree that JIRA is the place for this. But, I don't think we need a
new component. There's already a Test issue type and a Test component. I
think there just needs to be some vigilance on the part of people
checking the tests to file issues in JIRA if they persist more than a
few days.
Also, looking in JIRA, a lot of the issues marked issue type "Test",
component Test should probably be marked type "Improvement".
andrew
