Hi everyone -

Many months ago, the ON test sponsors sat down with Jim Pugsley, Mark
Nelson, John Beck, Miguel Ulloa and myself to clarify some testing
policies for ON RTIs, as it was found that these were not being applied
consistently which was leading to problems with test suites rotting
or bugs not being found early in the release process.

Out of this came the new "T" (Test) impact value in webRTI and
new instructions for developers and CRT advocates to help make
sure we keep (Open)Solaris a quality release at all times.

Here is the new information on testing that has been added to:
http://opensolaris.org/os/community/on/crt/rti-nits/

* Testing
         Developers are responsible for validating their changes
         prior to integration. This work should be described in
         the "Test Results" section of the RTI.

         Developers are also responsible for anticipating the need for
         ongoing regression testing of their changes.

         These considerations should be described in the "Comments"
         section of the RTI, and should include:

         * Changes to existing functionality, such that existing test
           suites need to be modified.

         * New functionality, such that new test suites will be needed.

         If either of these is the case, the "T" (Test Impact) button
         should be selected in your RTI.

         If you require new tests or significant modifications, please
         contact ON Test Sponsors and the RTI-test-review at sun.com before
         submitting your RTI. If you're not sure what constitutes a
         "significant" modification, please consult the same test sponsor
         group for clarification.

         If your changes are minor, file the appropriate bugs against the test
         suites and implement the change yourself. If implementing the change
         yourself is not practical, contact ON Test Sponsors and the
         RTI-test-review at sun.com to discuss potential assistance. List the CR
         number(s) in the "Comments" section of the RTI, and discuss the
         regression testing implications with your CRT advocate.

Please let me know if you have any questions.

Thank you,

Valerie, CRT Chair
-- 
Valerie Fenwick, http://blogs.sun.com/bubbva/ @bubbva
Solaris Security Technologies, Developer, Sun Microsystems, Inc.
17 Network Circle, Menlo Park, CA, 94025.

Reply via email to