Presentation is loading. Please wait.

Presentation is loading. Please wait.

COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Design & Documentation Adrian Marshall.

Similar presentations


Presentation on theme: "COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Design & Documentation Adrian Marshall."— Presentation transcript:

1 COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Design & Documentation Adrian Marshall

2 COMP8130 and 4130Adrian Marshall Test Design Logical grouping of tests Test size Modular test design Test class checklists Prioritisation of tests Test coverage

3 COMP8130 and 4130Adrian Marshall Test Design Group Tests by Test classes  White, black, grey box Focus areas  Functionality  Usability  Reliability  Performance D, I, A, T (demo, inspection, analysis, test)

4 COMP8130 and 4130Adrian Marshall Test Design Requirements testing Group by: Similar functions Similar set-up conditions Minimise verification of a requirement across multiple tests / test cases Manage requirements coverage (and traceability) in the design

5 COMP8130 and 4130Adrian Marshall Test Design Size of tests: Aim to have self-contained tests that can be executed within an hour Where possible have pre-established test data Ensure tests have set-up and re-set conditions at the end of the test Use (develop) test class checklists for test design guidance

6 COMP8130 and 4130Adrian Marshall Test Design Prioritisation of tests Functional criticality Build sequence Test coverage Criticality Complexity Product history

7 COMP8130 and 4130Adrian Marshall Test Design Test class checklists Knowledge base of verification Environment characteristics Functional focus Identifies testing at various levels

8 COMP8130 and 4130Adrian Marshall Test Design In small groups develop some checklists for the following test classes: HMI (Human Machine Interface) functionality COTS (Commercial off the Shelf) software Security (encryption, authentication, control)

9 COMP8130 and 4130Adrian Marshall Test Documentation Why do we document? Communication Repeatability Records of what needs to be done and what was done To manage test coverage

10 COMP8130 and 4130Adrian Marshall IEEE Test Documentation Set IEEE 829/ AS 4006 Planning & preparation Test Plans Test Design Specifications Test Case Specifications Test Procedure Specifications Execution & reporting Test Item Transmittal Report Test Log Test Incident Report Test Summary Report Other useful documents Test Verification Matrix Test Activity Measurement Report….

11 COMP8130 and 4130Adrian Marshall Test Documentation Other terms for test documents: Test Specifications Test Descriptions

12 COMP8130 and 4130Adrian Marshall Test Documentation Test Plans Master Test Plan Define testing at all levels Avoid needless overlaps and dangerous gaps Defines subordinate test plans Consists of test concept and summary test plan Can be delivered in multiple phases

13 COMP8130 and 4130Adrian Marshall Test Documentation Other Test Plans Plan tests for: sub-systems, major functional groups, and/or test harnesses

14 COMP8130 and 4130Adrian Marshall Test Documentation Test Design / Test Case specification Defines test design and major test cases Describes how the tests are to be run Details the test environment Describes the test cases (not to a procedural level), aims and objectives

15 COMP8130 and 4130Adrian Marshall Test Documentation Test Design and Case specification 1INTRODUCTION3 2REFERENCES3 TEST APPROACH3 3.1Test design3 3.2Test Conduct3 3.2.1Test Readiness3 3.2.2Test Execution Strategy3 3.2.3Pass / Fail determination3 3.3Test Reporting3

16 COMP8130 and 4130Adrian Marshall Test Documentation Test Case spec (contd) 4TEST ENVIRONMENT3 5REQUIREMENTS3 6TEST DESCRIPTION3 6.1Test Name 1 6.2Test Name 2 7DEFINITIONS, ABBREVIATIONS AND ACRONYMS3

17 COMP8130 and 4130Adrian Marshall Test Documentation Test Case spec (contd) APPENDIX A: HARDWARE/SOFTWARE CONFIGURATIONS3 APPENDIX B: SOFTWARE SETUP3 APPENDIX C: TEST DATA3

18 COMP8130 and 4130Adrian Marshall Test Documentation Test Procedures Include in Test Case (or have as a separate document) Can have delivery in multiple phases Describes the test steps Can be very prescriptive (beware of maintenance of such procedures) High level procedures may not be very repeatable (good and bad with this)

19 COMP8130 and 4130Adrian Marshall Test Documentation Test Logs / test record Identify actual test schedule and test duration Describe software and hardware versions Identify any deviations from the test procedures List who conducted the tests and any witnesses (eg customer, QA) Can be included in the case/ procedure document

20 COMP8130 and 4130Adrian Marshall Test Documentation Incident/defect reports Describe the issues raised To include: Title Adequate description of the issue Test reference Configuration info (software/ hardware versions, test data)

21 COMP8130 and 4130Adrian Marshall Test Documentation Incident/defect reports To include: Priority / severity information Who assigned to Status of the issue (open, under investigation, being fixed, fixed, closed etc. Dates (open, closed)

22 COMP8130 and 4130Adrian Marshall Test Documentation Incident/defect reports Should not have restrictions on creation Should only be closed the “raiser” or delegate

23 COMP8130 and 4130Adrian Marshall Test Documentation Test Reports Identify:  What was tested  When  By whom  On what  Outcomes (pass / fail)  Issues (reference defect number)

24 COMP8130 and 4130Adrian Marshall Test Documentation Test Reports Written on conclusion of test Aimed to report upwards Report recommendations should be documented separately

25 COMP8130 and 4130Adrian Marshall Test Verification Matrix Maps the test Plans/designs cases procedures to the project requirements to ensure that all testable requirements are verified and to manage requirement changes…. Test Documentation

26 COMP8130 and 4130Adrian Marshall Activity Measurement Report Quantifies the testing activities and their results : e.g. hours per activity start and end dates number of defects detected defect trends analysis of testing activities against plans…. Test Documentation

27 COMP8130 and 4130Adrian Marshall Summary Design Define methods, priorities, logical groupings, size of tests, test coverage, and test environment / tools Use / develop checklists Documentation Pre execution - Plans, cases, procedures Execution – logs Post execution – reports Documents communicate, provide repeatability, aid in management of test coverage (needless overlaps and dangerous gaps) Aim for the document is to support test execution not be a distraction to it.


Download ppt "COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Design & Documentation Adrian Marshall."

Similar presentations


Ads by Google