https://dev.eiffel.com/index.php?action=history&feed=atom&title=Category_talk%3ATesting 2026-05-25T21:30:52Z Revision history for this page on the wiki MediaWiki 1.24.1 https://dev.eiffel.com/index.php?title=Category_talk:Testing&diff=8564&oldid=prev 2007-05-30T17:55:20Z

<p></p> <table class='diff diff-contentalign-left'> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr style='vertical-align: top;'> <td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td> <td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 17:55, 30 May 2007</td> </tr><tr><td colspan="2" class="diff-lineno">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">=Overview=</del></div></td><td colspan="2">&#160;</td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of the release cycle are entirely devoted to testing. The general organization is described below.</del></div></td><td colspan="2">&#160;</td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"></del></div></td><td colspan="2">&#160;</td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">At this level of the development all testing is performed by a team member '''other''' than the developer of the corresponding system or subsystem. The testing process is formalized:</del></div></td><td colspan="2">&#160;</td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*For each system and subsystem, a [http://eiffelsoftware.origo.ethz.ch/testing/plan/ '''Test Plan'''] is created accordingly.</del></div></td><td colspan="2">&#160;</td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*The test plan is made of a number of descriptions of tests to be run, each known as a&#160; [http://eiffelsoftware.origo.ethz.ch/testing/tcs/ '''Test Case Specifications (TCS)''']. A TCS specifies a test scenario; it is not related to any particular execution of that scenario.</del></div></td><td colspan="2">&#160;</td></tr> <tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].</del></div></td><td colspan="2">&#160;</td></tr> </table>

Manus https://dev.eiffel.com/index.php?title=Category_talk:Testing&diff=8563&oldid=prev 2007-05-30T17:55:05Z

<p></p> <p><b>New page</b></p><div>=Overview=<br /> <br /> A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of the release cycle are entirely devoted to testing. The general organization is described below.<br /> <br /> At this level of the development all testing is performed by a team member '''other''' than the developer of the corresponding system or subsystem. The testing process is formalized:<br /> *For each system and subsystem, a [http://eiffelsoftware.origo.ethz.ch/testing/plan/ '''Test Plan'''] is created accordingly.<br /> *The test plan is made of a number of descriptions of tests to be run, each known as a [http://eiffelsoftware.origo.ethz.ch/testing/tcs/ '''Test Case Specifications (TCS)''']. A TCS specifies a test scenario; it is not related to any particular execution of that scenario.<br /> *The testing process consists of running these test scenarios; the result of any such run is a [http://eiffelsoftware.origo.ethz.ch/testing/ '''Test Run Report (TRR)'''].</div>

Manus