5. Features Not To Be Tested
Within "5. Features Not To Be Tested" you define which of the features of the system or sub-system will NOT be testing. This is necessary so as to avoid later confusion when stakeholders thought something would be tested, but was not.
Sample Text for 5. Features Not To Be Tested
An example for a Library Management System is:
|Item Being Tested||Business Scenarios NOT Being Tested|
|Borrowers sub-system||Maintaining the user records|
|The circulation sub-system||Setting up of holiday dates|
|The catalogue sub-system||Assigning loan periods|
Other Articles on SCOPE
SCOPE is one of the five aspects of a test plan. Other articles on it are:
- 3. Test Items gives guidance on what to put in this section of a test plan.
- 4. Features to be Tested gives guidance on what features are in relation to test items.
- Basics of Project Plans gives further information on item 2:"Long or Unrealistic Timescales" and item 4:"Scope Creep" as two of the five key characteristics of a project plan and the importance of balancing them.
- Verification and Validation has further information on item 6:"Poor Testing" by explaining what the terms Verification and Validation mean.