|
|
Line 1: |
Line 1: |
− | =Overview=
| |
| | | |
− | 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.
| |
− |
| |
− | 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:
| |
− | *For each system and subsystem, a [http://eiffelsoftware.origo.ethz.ch/testing/plan/ '''Test Plan'''] is created accordingly.
| |
− | *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.
| |
− | *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)'''].
| |