On Tue, 4 Aug 2009, Sebastien Roy wrote: > On Fri, 2009-06-12 at 13:39 -0700, Valerie Bubb Fenwick wrote: >> Sorry for the delay in following up with you. > > And I'm reciprocating the delay. :-)
I take your 2 month delay and raise by another 2 months ;-) (wow, the things I find in my inbox on slow days at work... ) >> As you can now see, >> the RTI nits page has been updated with the language agreed upon >> with the ON test sponsor folks, which happened before your mail came >> out. >> >> I believe your second bullet is adequately covered in the new >> nits text, but I don't think the first is fully covered. Could you >> look at the new text at let me know what, if any, additional testing >> text you want? > > My initial concern had to do with a flurry of RTIs that had no testing > details in them (i.e. "I did some testing and it passed"). In most > cases the RE has done proper testing, but in any case there's simply no > way for the RTI advocate to evaluate the extent of the testing and make > a decision regarding its adequacy. There needs to be documentation of > what was tested and how, and the results of the testing. It should be > shrink-to-fit, but the basic information should be there. > > I'd suggest something like: > > * Test Results > * This section should contain enough information for the CRT > advocate to evaluate if testing was adequate. Pointers to logs of > automated tests or terminal output of manual tests are welcome, > along with a high-level summary. For a simple fix, a description > of the testing methodology is fine. In all cases, a statement of > the form, "I tested the code and it passed" is inadequate. This has been added. More & more information is getting added here - I'd like to add anchors or something, but not sure if that's possible yet with xwiki. A former ON10 update techlead is working on more information to add here as well along the lines of "how to get your patch RTI accepted and not put on hold 8 times..." :) Valerie -- Valerie Fenwick, http://blogs.sun.com/bubbva/ @bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025.
