Generally: I sympathize and approve of your suggestions. Nits:
Sebastien> Logs of automated Sebastien> tests, or terminal output of manual tests are welcome. Change that to "Pointers to ..., along with a high-level summary." I often get RTIs with pointers to several test log files that are very long and somewhat difficult to parse, so a) putting them in-line is impractical, and b) providing an executive summary makes my work a lot easier. Sebastien> If tests could be added to an existing automated test suite to Sebastien> facilitate in testing the affected code, then either integrate Sebastien> such a test, or file an RFE against the test suite detailing Sebastien> what is missing. Without that, code-coverage of existing Sebastien> test suites will never improve, and bugs will perpetually be Sebastien> re-introduced in the same areas due to lack of test coverage. All true and good suggestions, but in that case, the "T" impact button should be selected, and the CR #(s) for new or updated test suites should be listed in the Comments section of the RTI. -- John http://blogs.sun.com/jbeck
