source: rtems-docs/eng/test-plan.rst @ 6682434

5
Last change on this file since 6682434 was 6682434, checked in by Joel Sherrill <joel@…>, on 12/20/18 at 15:17:09

Eliminate UTF-8 characters except superscripted 2 in i2c

  • Property mode set to 100644
File size: 1.4 KB
Line 
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
7Software Test Plan Assurance and Procedures
8********************************************
9
10Testing and Coverage
11====================
12
13Testing to verify that requirements are implemented is a critical part of
14the high integrity processes. Similarly, measuring and reporting source
15and decision path coverage of source code is critical.
16
17Needed improvements to the RTEMS testing infrastructure should be done
18as part of the open project. Similarly, improvements in RTEMS coverage
19reporting should be done as part of the open project. Both of these
20capabilities are part of the RTEMS Tester toolset.
21
22Assuming that a requirements focused test suite is added to the open
23RTEMS, tools will be needed to assist in verifying that requirements are
24"fully tested." A fully tested requirement is one which is implemented
25and tested with associated logical tracing. Tools automating this analysis
26and generating reporting and alerts will be a critical part of ensuring
27the master technical data does not bit rot.
28
29Must use tools from:
30
31TBD - Change URL to git.rtems.org and list support tools
32RTEMS Tools Project: https://github.com/RTEMS/rtems-tools
33
34
35Scope, Procedures, Methodologies, Tools
36TBD - Write content
37
38.. COMMENT: Subsections
39.. toctree::
40
41    test-suites
42    tester
Note: See TracBrowser for help on using the repository browser.