1 | .. comment SPDX-License-Identifier: CC-BY-SA-4.0 |
---|
2 | |
---|
3 | .. COMMENT: COPYRIGHT (c) 2018. |
---|
4 | .. COMMENT: RTEMS Foundation, The RTEMS Documentation Project |
---|
5 | |
---|
6 | |
---|
7 | Software Test Plan Assurance and Procedures |
---|
8 | ******************************************** |
---|
9 | |
---|
10 | Testing and Coverage |
---|
11 | ==================== |
---|
12 | |
---|
13 | Testing to verify that requirements are implemented is a critical part of |
---|
14 | the high integrity processes. Similarly, measuring and reporting source |
---|
15 | and decision path coverage of source code is critical. |
---|
16 | |
---|
17 | Needed improvements to the RTEMS testing infrastructure should be done |
---|
18 | as part of the open project. Similarly, improvements in RTEMS coverage |
---|
19 | reporting should be done as part of the open project. Both of these |
---|
20 | capabilities are part of the RTEMS Tester toolset. |
---|
21 | |
---|
22 | Assuming that a requirements focused test suite is added to the open |
---|
23 | RTEMS, tools will be needed to assist in verifying that requirements are |
---|
24 | âfully tested.â A fully tested requirement is one which is implemented |
---|
25 | and tested with associated logical tracing. Tools automating this analysis |
---|
26 | and generating reporting and alerts will be a critical part of ensuring |
---|
27 | the master technical data does not bit rot. |
---|
28 | |
---|
29 | Must use tools from: |
---|
30 | |
---|
31 | TBD - Change URL to git.rtems.org and list support tools |
---|
32 | RTEMS Tools Project: https://github.com/RTEMS/rtems-tools |
---|
33 | |
---|
34 | |
---|
35 | Scope, Procedures, Methodologies, Tools |
---|
36 | TBD - Write content |
---|
37 | |
---|
38 | .. COMMENT: Subsections |
---|
39 | .. toctree:: |
---|
40 | |
---|
41 | test-suites |
---|
42 | tester |
---|