|
168 | 168 | </ul> |
169 | 169 | </div> |
170 | 170 |
|
171 | | - <!-- |
172 | | - <div class="page"> |
173 | | - <h2 id="section_3"><span>3</span>Scope of Test Execution</h2> |
174 | | - <p>This section will be manually filled before test execution. Please describe the scope of Test case execution in case not all test cases in this document will be executed.</p> |
175 | | - {{#if data.sections.sec3.show}} |
176 | | - <table style="border: 0px; padding: 0px; margin: 0px"> |
177 | | - <tr> |
178 | | - <td class="content-wrappable" style="border: 0px; padding: 0px; margin: 0px;">{{{data.sections.sec3.content}}}</td> |
179 | | - </tr> |
180 | | - </table> |
181 | | - {{else}} |
182 | | - <p>Not mandatory</p> |
183 | | - {{/if}} |
184 | | - </div> |
185 | | - |
186 | | - <div class="page"> |
187 | | - <h2 id="section_4"><span>4</span>Test Execution Instructions</h2> |
188 | | - <p>In the case that the test execution is fully automated, Jenkins (Technical Role) shall:</p> |
189 | | - <ul> |
190 | | - <li>Execute the code base test cases</li> |
191 | | - <li>Record the test results and evidence after the execution and include them in the XUnit file</li> |
192 | | - <li>Following Good Documentation Practices</li> |
193 | | - <li>Mark the test cases as a "Fail" or a "Pass"</li> |
194 | | - <li>Stop the test execution if one of the test cases has failed</li> |
195 | | - <li>Report back the test execution results to the Test Management Tool</li> |
196 | | - </ul> |
197 | | - |
198 | | - <p>Preparation of the test document for execution:</p> |
199 | | - <ul> |
200 | | - <li>Test results must be documented on a paper copy or a printout of the approved test case document.</li> |
201 | | - <li>The copy or printout must include the approval signatures (handwritten or electronic signature page) for the test cases</li> |
202 | | - <li>Pages of test cases that will not be executed may be removed prior to start of test execution. This must be documented in section 3.</li> |
203 | | - <li>No pages of the copy or printout must be removed or replaced during test execution.</li> |
204 | | - <li>Pages may be added during execution, e.g. if test cases need to be re-executed. Reason for the addition must be documented on these additional pages.</li> |
205 | | - </ul> |
206 | | - <p>For the documentation of test results the following rules of good documentation practice need to be fulfilled:</p> |
207 | | - <ul> |
208 | | - <li>Results and other entries have to be recorded handwritten.</li> |
209 | | - <li>Initials, signatures and dates provided by the tester have to be documented handwritten.</li> |
210 | | - <li>Handwritten entries must be made in clear, legible, indelible way.</li> |
211 | | - <li>Records must be made or completed at the time each action is taken and in such a way that all significant activities are traceable.</li> |
212 | | - <li>Any alteration made to an entry must be signed and dated; the alteration should permit the reading of the original information. Where appropriate, the reason for the alteration should be recorded.</li> |
213 | | - </ul> |
214 | | - <p>Creation of supporting evidence:</p> |
215 | | - <ul> |
216 | | - <li>Supporting evidence must be printed, dated and signed by the Tester, and labelled with test case # and step # on the day of test execution.</li> |
217 | | - <li>Screen shots or other objective evidence made by one tester may be collected e.g. in a MS Word document, but must be printed and dated/signed by the Tester on the day of test execution. Alternatively, these can be signed in IDEAforCON directly, as long as the Tester signs the Word document with the screenshots on the day of test execution in IDEAforCON.</li> |
218 | | - <li>In case of electronically recorded evidence (e.g. video files), the test results must be unambiguously linked to the objective evidence, summarized on a printout and signed on the day of test execution.</li> |
219 | | - </ul> |
220 | | - <p>The column "Initials / Date" only needs to be filled if</p> |
221 | | - <ul> |
222 | | - <li>Test steps in a test case are executed by more than one tester: Each tester writes initials/dates for all steps executed into the column.</li> |
223 | | - <li>Test steps in a test case are executed on more than one day: the tester writes the date of execution for every step into the column.</li> |
224 | | - </ul> |
225 | | - </div> |
226 | | - --> |
227 | | - |
228 | 171 | <div class="page"> |
229 | 172 | <h2 id="section_3"><span>3</span>Test Cases</h2> |
230 | 173 | <h3 id="section_3_1"><span>3.1</span>Integration Test Cases</h3> |
|
259 | 202 | <th>Instructions</th> |
260 | 203 | <th>Expected result</th> |
261 | 204 | <th>Actual result</th> |
262 | | - <th>Initials / Date</th> |
263 | 205 | </thead> |
264 | 206 | <tbody> |
265 | 207 | {{#each steps}} |
|
268 | 210 | <td class="content-wrappable">{{{step}}}</td> |
269 | 211 | <td class="content-wrappable">{{{result}}}</td> |
270 | 212 | <td class="content-wrappable">{{{../actualResult}}}</td> |
271 | | - <td class="content-wrappable">Jenkins {{{../timestamp}}}</td> |
272 | 213 | </tr> |
273 | 214 | {{/each}} <!-- end test steps --> |
274 | 215 | </tbody> |
|
331 | 272 | <th>Instructions</th> |
332 | 273 | <th>Expected result / Evidence</th> |
333 | 274 | <th>Actual result</th> |
334 | | - <th>Initials / Date</th> |
335 | 275 | </thead> |
336 | 276 | <tbody> |
337 | 277 | {{#each steps}} |
|
340 | 280 | <td class="content-wrappable">{{{step}}}</td> |
341 | 281 | <td class="content-wrappable">{{{result}}}</td> |
342 | 282 | <td class="content-wrappable">{{{actualResult}}}</td> |
343 | | - <td>Jenkins {{{../timestamp}}}</td> |
344 | 283 | </tr> |
345 | 284 | {{/each}} <!-- end test steps block --> |
346 | 285 | </tbody> |
|
0 commit comments