Difference between revisions of "Category:Testing"
| Line 1: | Line 1: | ||
| − | + | A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a release cycle are entirely devoted to testing. The general organization is described below. | |
| − | + | ||
| − | A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of | + | |
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: | 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: | ||
Revision as of 08:55, 30 May 2007
A systematic testing process is necessary to produce a timely release with a high level of quality. The last six weeks of a 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 Test Plan is created accordingly.
- The test plan is made of a number of descriptions of tests to be run, each known as a 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 Test Run Report (TRR).
Pages in category "Testing"
The following 15 pages are in this category, out of 15 total.
CG |
G cont. |
G cont.RT |
