1、BSI Standards Publication BS ISO/IEC/IEEE 29119-4:2015 Software and systems engineering Software testing Part 4: Test techniquesBS ISO/IEC/IEEE 29119-4:2015 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC/IEEE 29119-4:2015. It supersedes BS 7925-2:1998 wh
2、ich is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary p
3、rovisions of a contract. Users are responsible for its correct application. The British Standards Institution 2015. Published by BSI Standards Limited 2015 ISBN 978 0 580 76329 8 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was pu
4、blished under the authority of the Standards Policy and Strategy Committee on 31 December 2015. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dBS ISO/IEC/IEEE 29119-4:2015Reference number ISO/IEC/IEEE 29119-4:2015(E) ISO/IEC 2015 IEEE 2015 INTERNATIONAL STANDARD ISO/IEC/
5、IEEE 29119-4 First edition 2015-12-01 Software and systems engineering Software testing Part 4: Test techniques Ingnierie du logiciel et des systmes Essais du logiciel Partie 4: Techniques dessai BS ISO/IEC/IEEE 29119-4:2015 ISO/IEC/IEEE 29119-4:2015(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015 IEEE
6、 2015 All rights reserved. Unless otherwise specif ied, no part of this publication may be reproduced or utilized in any form or by an y means, electronic or mechanical, including photocopyi ng and microfilm, without permission in writing from ISO, IEC or IEEE at the resp ective address below. Insti
7、tute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York NY 10016-5997, USA E-mail stds.iprieee.org Web www.ieee.org IEC Central Office 3, rue de Varemb CH-1211 Geneva 20 Switzerland E-mail inmailiec.ch Web www.iec.ch ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier,
8、 Geneva, Switzerland Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 copyrightiso.org www.iso.org Published in Switzerland ii ISO/IEC 2015 All rights reserved IEEE 2015 All rights reservedBS ISO/IEC/IEEE 29119-4:2015ISO/IEC/IEEE 29119-4:2015(E)Foreword v Introduction vi 1 Scope . 1 2 Conformance . 1 2.
9、1 Intended Usage . 1 2.2 Full Conformance 1 2.3 Tailored Conformance 1 3 Normative References . 1 4 T erms and Definitions 2 5 Test Design Techniques . 4 5.1 Overview 4 5.2 Specification-Based Test Design Techniques 7 5.2.1 Equivalence Partitioning . 7 5.2.2 Classification Tree Method 8 5.2.3 Bounda
10、ry Value Analysis 9 5.2.4 Syntax Testing .11 5.2.5 Combinatorial Test Design Techniques .12 5.2.6 Decision Table Testing15 5.2.7 Cause-Effect Graphing 15 5.2.8 State Transition Testing 16 5.2.9 Scenario Testing 17 5.2.10 Random Testing .18 5.3 Structure-Based Test Design Techniques 18 5.3.1 Statemen
11、t Testing 18 5.3.2 Branch Testing 19 5.3.3 Decision Testing .20 5.3.4 Branch Condition Testing 20 5.3.5 Branch Condition Combination Testing 21 5.3.6 Modified Condition Decision Coverage (MCDC) Testing 21 5.3.7 Data Flow Testing .22 5.4 Experience-Based Test Design Techniques .25 5.4.1 Error Guessin
12、g 25 6 Test Coverage Measurement .25 6.1 Overview .25 6.2 Test Measurement for Specification-Based Test Design Techniques 26 6.2.1 Equivalence Partition Coverage .26 6.2.2 Classification Tree Method Coverage 26 6.2.3 Boundary Value Analysis Coverage .26 6.2.4 Syntax Testing Coverage .26 6.2.5 Combin
13、atorial Test Design Technique Coverage .27 6.2.6 Decision Table Testing Coverage .27 6.2.7 Cause-Effect Graphing Coverage .28 6.2.8 State Transition Testing Coverage .28 6.2.9 Scenario Testing Coverage 28 6.2.10 Random Testing Coverage 28 6.3 Test Measurement for Structure-Based Test Design Techniqu
14、es .29 6.3.1 Statement Testing Coverage 29 6.3.2 Branch Testing Coverage 29 6.3.3 Decision Testing Coverage 29 6.3.4 Branch Condition Testing Coverage .29 6.3.5 Branch Condition Combination Testing Coverage .29 6.3.6 Modified Condition Decision (MCDC) Testing Coverage 30 ISO/IEC 2015 All rights rese
15、rved iii IEEE 2015 All rights reserved Contents PageBS ISO/IEC/IEEE 29119-4:2015ISO/IEC/IEEE 29119-4:2015(E)6.3.7 Data Flow Testing Coverage 30 6.4 Test Measurement for Experience-Based Testing Design Techniques.31 6.4.1 Error Guessing Coverage .31 Annex A (informative) Testing Quality Characteristi
16、cs 32 Annex B (informative) Guidelines and Ex amples for the A pplication of Specification-Based Test Design Techniques 43 Annex C (informative) Guidelines and Examples for the Application of Structure-Based Test Design Techniques 103 Annex D (informative) Guidelines and Examples for the Application
17、 of Experience-Based Test Design Techniques 126 Annex E (informative) Guidelines and Examples for the Application of Interchangeable Test Design Techniques 129 Annex F (informative) Test Design Technique Coverage Effectiveness 133 Annex G (informative) ISO/IEC/IEEE 29119-4 and BS 7925-2 Test Design
18、Technique Alignment 135 Bibliography .137 iv ISO/IEC 2015 All rights reserved IEEE 2015 All rights reservedBS ISO/IEC/IEEE 29119-4:2015ISO/IEC/IEEE 29119-4:2015(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the speci
19、alized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical co
20、mmittees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The proce
21、dures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rul
22、es of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent righ
23、ts identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an exp
24、lanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this do
25、cument is ISO/IEC JTC 1, Information technology, SC 7, Software and Systems Engineering. ISO/IEC/IEEE 29119 consists of the following standards, under the general title Software and Systems Engineering Software Testing: Part 1: Concepts and definitions Part 2: Test processes Part 3: Test documentati
26、on Part 4: Test techniques The following parts are under preparation: Part 5: Keyword-driven testing ISO/IEC 2015 All rights reserved v IEEE 2015 All rights reservedBS ISO/IEC/IEEE 29119-4:2015ISO/IEC/IEEE 29119-4:2015(E) Introduction The purpose of this part of ISO/IEC/IEEE 29119 is to provide an I
27、nternational Standard that defines software test design techniques (also known as test case design techniques or test methods) that can be used within the test design and implementation process that is defined in ISO/IEC/IEEE 29119-2. This part of ISO/IEC/IEEE 29119 does not prescribe a process for
28、test design and implementation; instead, it describes a set of techniques that can be used within ISO/IEC/IEEE 29119-2. The intent is to describe a series of techniques that have wide acceptance in the software testing industry. The test design techniques presented in this part of ISO/IEC/IEEE 29119
29、 can be used to derive test cases that, when executed, generate evidence that test item requirements have been met and/or that defects are present in a test item (i.e. that requirements have not been met). Risk-based testing could be used to determine the set of techniques that are applicable in spe
30、cific situations (risk-based testing is covered in ISO/IEC/IEEE 29119-1 and ISO/IEC/IEEE 29119-2). NOTE A “test item” is a work product that is being tested (see ISO/IEC/IEEE 29119-1). EXAMPLE 1 “Test items” include systems, software items, objects, classes, requirements documents, design specificat
31、ions, and user guides. Each technique follows the test design and implementation process that is defined in ISO/IEC/ IEEE 29119-2 and shown in Figure 1. Of the activities in this process, ISO/IEC/IEEE 29119-4 provides guidance on how to implement the following activities in detail for each technique
32、 that is described: Derive Test Conditions (TD2); Derive Test Coverage Items (TD3); Derive Test Cases (TD4). A test condition is a testable aspect of a test item, such as a function, transaction, feature, quality attribute, or structural element identified as a basis for testing. This determination
33、can be achieved by agreeing with stakeholders which attributes are to be tested or by applying one or more test design techniques. EXAMPLE 2 If a test completion criterion for state transition testing was identified that required coverage of all states then the test conditions could be the states th
34、e test item can be in. Other examples of test conditions are equivalence classes and boundaries between them. Test coverage items are attributes of each test condition that can be covered during testing. A single test condition may be the basis for one or more test coverage items. EXAMPLE 3 If a spe
35、cific boundary is identified as a test condition, then the corresponding test coverage items could be the boundary itself and immediately either side of the boundary. A test case is a set of preconditions, inputs (including actions, where applicable), and expected results, developed to determine whe
36、ther or not the covered part of the test item has been implemented correctly. Specific (normative) guidance on how to implement the other activities in the test design & implementation process of ISO/IEC/IEEE 29119-2, including activities TD1 (Identify Feature Sets), TD5 (Assemble Test Sets), and TD
37、6 (Derive Test Procedures), is not included in Clauses 5 or 6 of this part of ISO/IEC/IEEE 29119 because the process is the same for all techniques.vi ISO/IEC 2015 All rights reserved IEEE 2015 All rights reservedBS ISO/IEC/IEEE 29119-4:2015ISO/IEC/IEEE 29119-4:2015(E) Figure 1 ISO/IEC/IEEE 29119-2
38、Test Design and Implementation Process ISO/IEC/TR 19759 (SWEBOK) defines two types of requirements: functional requirements and quality requirements. ISO/IEC 25010 defines eight quality characteristics (including functionality) that can be used to identify types of testing that may be applicable for
39、 testing a specific test item. Annex A provides example mappings of test design techniques that apply to testing quality characteristics defined in ISO/IEC 25010. Experience-based testing practices like exploratory testing and other test practices such as model-based testing are not defined in this
40、part of ISO/IEC/IEEE 29119 because this part of ISO/IEC/IEEE 29119 only describes techniques for designing test cases. Test practices such as exploratory testing are described in ISO/IEC/IEEE 29119-1. Templates and examples of test documentation that are produced during the testing process are defin
41、ed in ISO/IEC/IEEE 29119-3 Test Documentation. The test techniques in this part of ISO/IEC/IEEE 29119 do not describe how test cases should be documented (e.g. they do not include information or guidance on assigning unique identifiers, test case descriptions, priorities, traceability, or pre-condit
42、ions). Information on how to document test cases can be found in ISO/IEC/IEEE 29119-3. This part of ISO/IEC/IEEE 29119 aims to provide stakeholders with the ability to design test cases for the testing of software in any organization. ISO/IEC 2015 All rights reserved vii IEEE 2015 All rights reserve
43、dBS ISO/IEC/IEEE 29119-4:2015BS ISO/IEC/IEEE 29119-4:2015Software and systems engineering Software testing Part 4: Test techniques 1 Scope This part of ISO/IEC/IEEE 29119 defines test design techniques that can be used during the test design and implementation process that is defined in ISO/IEC/IEEE
44、 29119-2. This part of ISO/IEC/IEEE 29119 is intended for, but not limited to, testers, test managers, and developers, particularly those responsible for managing and implementing software testing. 2 Conformance 2.1 Intended Usage The normative requirements in this part of ISO/IEC/IEEE 29119 are con
45、tained in Clauses 5 and 6. It is recognised that particular projects or organizations may not need to use all of the techniques defined by this standard. Therefore, implementation of this standard typically involves selecting a set of techniques suitable for the project or organization. There are tw
46、o ways that an organization or individual can claim conformance to the provisions of this standard full conformance or tailored conformance. The organization or individual shall assert whether full or tailored conformance to this standard is claimed. 2.2 Full Conformance Full conformance is achieved
47、 by demonstrating that all of the requirements (i.e. shall statements) of the chosen (non-empty) set of techniques in Clause 5 and/or the corresponding test coverage measurement approaches in Clause 6 have been satisfied. EXAMPLE An organization could choose to conform only to one technique, such as
48、 boundary value analysis. In this scenario, the organization would only be required to provide evidence that they have met the requirements of that one technique in order to claim conformance to this part of ISO/IEC/IEEE 29119. 2.3 Tailored Conformance Tailored conformance is achieved by demonstrati
49、ng that the chosen subset of requirements from the chosen (non-empty) set of techniques and/or corresponding test coverage measurement approaches have been satisfied. Where tailoring occurs, justification shall be provided (either directly or by reference) whenever the normative requirements of a technique defined in Clause 5 or measure defined in Clause 6 are not followed completely. All tailoring decisions shall be recorded with their rationale, including the consideration of any applicable
