From 1ae5e889fbf6e5e134402ab9fbdf5878dd9731e8 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 21 Nov 2018 10:39:04 -0600 Subject: Initial start of converting the Word outline to Rest Thanks to Scott Zemerick for the analysis and ideas that led to this. --- eng/test-plan.rst | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 eng/test-plan.rst (limited to 'eng/test-plan.rst') diff --git a/eng/test-plan.rst b/eng/test-plan.rst new file mode 100644 index 0000000..c85efd2 --- /dev/null +++ b/eng/test-plan.rst @@ -0,0 +1,42 @@ +.. comment SPDX-License-Identifier: CC-BY-SA-4.0 + +.. COMMENT: COPYRIGHT (c) 2018. +.. COMMENT: RTEMS Foundation, The RTEMS Documentation Project + + +Software Test Plan Assurance and Procedures +******************************************** + +Testing and Coverage +==================== + +Testing to verify that requirements are implemented is a critical part of +the high integrity processes. Similarly, measuring and reporting source +and decision path coverage of source code is critical. + +Needed improvements to the RTEMS testing infrastructure should be done +as part of the open project. Similarly, improvements in RTEMS coverage +reporting should be done as part of the open project. Both of these +capabilities are part of the RTEMS Tester toolset. + +Assuming that a requirements focused test suite is added to the open +RTEMS, tools will be needed to assist in verifying that requirements are +“fully tested.” A fully tested requirement is one which is implemented +and tested with associated logical tracing. Tools automating this analysis +and generating reporting and alerts will be a critical part of ensuring +the master technical data does not bit rot. + +Must use tools from: + +TBD - Change URL to git.rtems.org and list support tools +RTEMS Tools Project: https://github.com/RTEMS/rtems-tools + + +Scope, Procedures, Methodologies, Tools +TBD - Write content + +.. COMMENT: Subsections +.. toctree:: + + test-suites + tester -- cgit v1.2.3