Resolves CFTP-8

opendevstack · Jan 26, 2022 · cec8d39 · cec8d39
1 parent 64c9d69
commit cec8d39
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 21 deletions.
diff --git a/templates/CFTP-3.html.tmpl b/templates/CFTP-3.html.tmpl
@@ -164,13 +164,7 @@
         <p>The objective of the Integration Testing level is to verify whether the applicable components (e.g. modules, micro-services and/or systems) work well together and detect flaws in their interactions.</p>
 
         <h3 id="section_4_2"><span>4.2</span>Acceptance Testing</h3>
-        <p>Acceptance tests assert that a system does what the business intends it to do. They can be of functional (for testing user requirements) or non-functional kind (for testing, e.g., system availability, performance, or reliability).</p>
-
-        <h4 id="section_4_2_1"><span>4.2.1 </span>Functional Testing</h4>
-        <p>Functional testing ensures that a system satisfies any given functional (user) requirements.</p>
-
-        <h4 id="section_4_2_2"><span>4.2.2 </span>Non-Functional Testing</h4>
-        <p>Non-functional testing ensures that a system satisfies any given non-functional (operational) requirements. Examples for non-functional tests are: load tests, performance tests, security tests, and recovery tests.</p>
+        <p>Acceptance tests refer to functional (user) or non-functional (such as system availability, performance, reliability) requirements. Examples for non-functional acceptance tests are: load tests, performance tests, recovery tests.</p>
     </div>
 
     <div class="page">

diff --git a/templates/CFTP-4.html.tmpl b/templates/CFTP-4.html.tmpl
@@ -164,13 +164,7 @@
         <p>The objective of the Integration Testing level is to verify whether the applicable components (e.g. modules, micro-services and/or systems) work well together and detect flaws in their interactions.</p>
 
         <h3 id="section_4_2"><span>4.2</span>Acceptance Testing</h3>
-        <p>Acceptance tests assert that a system does what the business intends it to do. They can be of functional (for testing user requirements) or non-functional kind (for testing, e.g., system availability, performance, or reliability).</p>
-
-        <h4 id="section_4_2_1"><span>4.2.1 </span>Functional Testing</h4>
-        <p>Functional testing ensures that a system satisfies any given functional (user) requirements.</p>
-
-        <h4 id="section_4_2_2"><span>4.2.2 </span>Non-Functional Testing</h4>
-        <p>Non-functional testing ensures that a system satisfies any given non-functional (operational) requirements. Examples for non-functional tests are: load tests, performance tests, security tests, and recovery tests.</p>
+        <p>Acceptance tests refer to functional (user) or non-functional (such as system availability, performance, reliability) requirements. Examples for non-functional acceptance tests are: load tests, performance tests, recovery tests.</p>
     </div>
 
     <div class="page">

diff --git a/templates/CFTP-5.html.tmpl b/templates/CFTP-5.html.tmpl
@@ -164,13 +164,7 @@
         <p>The objective of the Integration Testing level is to verify whether the applicable components (e.g. modules, micro-services and/or systems) work well together and detect flaws in their interactions.</p>
 
         <h3 id="section_4_2"><span>4.2</span>Acceptance Testing</h3>
-        <p>Acceptance tests assert that a system does what the business intends it to do. They can be of functional (for testing user requirements) or non-functional kind (for testing, e.g., system availability, performance, or reliability).</p>
-
-        <h4 id="section_4_2_1"><span>4.2.1 </span>Functional Testing</h4>
-        <p>Functional testing ensures that a system satisfies any given functional (user) requirements.</p>
-
-        <h4 id="section_4_2_2"><span>4.2.2 </span>Non-Functional Testing</h4>
-        <p>Non-functional testing ensures that a system satisfies any given non-functional (operational) requirements. Examples for non-functional tests are: load tests, performance tests, security tests, and recovery tests.</p>
+        <p>Acceptance tests refer to functional (user) or non-functional (such as system availability, performance, reliability) requirements. Examples for non-functional acceptance tests are: load tests, performance tests, recovery tests.</p>
     </div>
 
     <div class="page">