I rename T Test in RTEMS Test and updated

https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf

with the attached patch.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

>From a5a3c8870293e646f7c373b69e831a5193b0d3df Mon Sep 17 00:00:00 2001
From: Sebastian Huber <sebastian.hu...@embedded-brains.de>
Date: Fri, 22 Mar 2019 09:51:29 +0100
Subject: [PATCH] eng: Rename T Test in RTEMS Test

---
 eng/test-framework.rst | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/eng/test-framework.rst b/eng/test-framework.rst
index 9e0560b..2730f6a 100644
--- a/eng/test-framework.rst
+++ b/eng/test-framework.rst
@@ -6,12 +6,12 @@
 Software Test Framework
 ***********************
 
-.. _TheTTestFramework:
+.. _RTEMSTestFramework:
 
-The T Test Framework
-====================
+The RTEMS Test Framework
+========================
 
-The `T Test Framework` helps you to write test suites.  It has the following
+The `RTEMS Test Framework` helps you to write test suites.  It has the following
 features:
 
 * Implemented in standard C11
@@ -127,7 +127,7 @@ as the test step 1 failed with a message of `"a test failure message"`.  The
 `E` line indicates the end of test case `a_test_case` resulting in a total of
 two test steps (`N`) and one test failure (`F`).  The test case execution
 duration (`D`) was 0.001657 seconds.  For test report details see:
-:ref:`Test Reporting <TheTTestFrameworkTestReporting>`.
+:ref:`Test Reporting <RTEMSTestFrameworkTestReporting>`.
 
 Test Fixture
 ------------
@@ -1427,7 +1427,7 @@ The same example with `T_VERBOSE` verbosity:
         E:d:N:6:F:0
         Z:xyz:C:4:N:9:F:3
 
-.. _TheTTestFrameworkTestReporting:
+.. _RTEMSTestFrameworkTestReporting:
 
 Test Reporting
 --------------
@@ -2110,8 +2110,8 @@ You know the failure count only after a complete test run.  This runs contrary
 to requirement `TF.Portability.Small.Memory`.  It is also a bit verbose
 (`TF.Reporting.Compact`).
 
-It is easy to convert a full test report generated by :ref:`The T Test
-Framework <TheTTestFramework>` to the JUnit XML format.
+It is easy to convert a full test report generated by :ref:`The RTEMS Test
+Framework <RTEMSTestFramework>` to the JUnit XML format.
 
 Test Anything Protocol
 ----------------------
@@ -2132,5 +2132,5 @@ You have to know in advance how many test statements you want to execute in a
 test case.  The problem with this format is that there is no standard way to
 provide auxiliary data such as test timing or a tracing report.
 
-It is easy to convert a full test report generated by :ref:`The T Test
-Framework <TheTTestFramework>` to the TAP format.
+It is easy to convert a full test report generated by :ref:`The RTEMS Test
+Framework <RTEMSTestFramework>` to the TAP format.
-- 
2.16.4

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to