System Design Document (SDD) Version <#.#>, Date <Month, Year> Requirements Traceability Matrix (RTM) Version <#.#>, Date <Month, Year> Risk Log Version <#.#>, Date <Month, Year> Items To Be Tested List those test items - software, hardware, and supporting product elements that serve as targets for testing. A test item may include source code, object code, job control code, control data, documentation, or a collection of these. Overview of Test Inclusions Provide a high-level list of the major target test items. This list should include both items produced directly by the project Development Team and, if applicable, as well as products being integrated into the information system or application. Refer to the Requirements Specification Document (RSD) to identify the requirements needed for testing items that those products rely on; For example, basic processor hardware, peripheral devices, operating systems, third-party products or components, and so forth. Consider grouping the list by category and assigning relative importance to each motivator. The following components and features and combinations of components and features will be tested: Overview of Test Exclusions Identify any items specifically excluded from testing. The following components and features and combinations of components and features will not be tested: Test Approach The Test Approach is the implementation of the Test Strategy. The Test Approach cites how the Development Team plans to cover the testing activities specified in the Product Build and Independent Test and Evaluation processes in ProPath. Product Component Test Briefly describe how the Developers perform Product Component Test, also known as Unit Test. Identify the responsible roles. For more information, see the Product Build process in ProPath. Component Integration Test Briefly describe how the Developers perform Component Integration Test. Identify the responsible roles. For more information, see the Product Build process in ProPath.
System Design Document (SDD) Version <#.#>, Date <Month, Year> Requirements Traceability Matrix (RTM) Version <#.#>, Date <Month, Year> Risk Log Version <#.#>, Date <Month, Year> Items To Be Tested List those test items - software, hardware, and supporting product elements that serve as targets for testing. A test item may include source code, object code, job control code, control data, documentation, or a collection of these. Overview of Test Inclusions Provide a high-level list of the major target test items. This list should include both items produced directly by the project Development Team and, if applicable, as well as products being integrated into the information system or application. Refer to the Requirements Specification Document (RSD) to identify the requirements needed for testing items that those products rely on; For example, basic processor hardware, peripheral devices, operating systems, third-party products or components, and so forth. Consider grouping the list by category and assigning relative importance to each motivator. The following components and features and combinations of components and features will be tested: Overview of Test Exclusions Identify any items specifically excluded from testing. The following components and features and combinations of components and features will not be tested: Test Approach The Test Approach is the implementation of the Test Strategy. The Test Approach cites how the Development Team plans to cover the testing activities specified in the Product Build and Independent Test and Evaluation processes in ProPath. Product Component Test Briefly describe how the Developers perform Product Component Test, also known as Unit Test. Identify the responsible roles. For more information, see the Product Build process in ProPath. Component Integration Test Briefly describe how the Developers perform Component Integration Test. Identify the responsible roles. For more information, see the Product Build process in ProPath.