ISO/IEC 30130:2016

INTERNATIONAL ISO/IEC
STANDARD 30130
First edition
Software engineering — Capabilities
of software testing tools
Ingénierie du logiciel — Capacités des outils d’essai de logiciel
PROOF/ÉPREUVE
Reference number
ISO/IEC 30130:2015(E)
©
ISO/IEC 2015
ISO/IEC 30130:2015(E)
© ISO/IEC 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2015 – All rights reserved

ISO/IEC 30130:2015(E)
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Object model for software testing tools. 2
4.1 Overview of the object model . 2
4.2 Test target . 3
4.3 Dynamic test execution entity . 3
4.4 Code analysis entity . 4
4.5 Test management entity . 4
5 Category of test entity . 5
5.1 Overview . 5
5.2 Categories of dynamic test execution entities . 5
5.2.1 Input for dynamic test execution . 5
5.2.2 Dynamic test execution . 5
5.2.3 Test data repository . 5
5.2.4 Test environment . 6
5.3 Categories of code analysis entities . 6
5.3.1 Input for code analysis . 6
5.3.2 Code analysis . 6
5.4 Categories of test management entities . 6
5.4.1 Test plan . 6
5.4.2 Test asset . 6
5.4.3 Quality record report . 6
5.4.4 Test completion report . 6
5.4.5 Verification and validation report . 6
5.4.6 Test status report . 6
6 Characteristics of software testing tools . 6
6.1 Overview . 6
6.2 Quality characteristics . 7
6.3 Granularity . 8
6.4 Other aspects of characteristics . 9
7 Capabilities of software testing tools . 9
7.1 Overview . 9
7.2 Dynamic test execution . 9
7.2.1 Input for dynamic test execution . 9
7.2.2 Dynamic Test Execution .10
7.2.3 Test data repository .11
7.2.4 Test Environment .12
7.3 Code analysis .13
7.3.1 Input for code analysis .13
7.3.2 Code analysis .13
7.4 Test management .14
7.4.1 Test plan .14
7.4.2 Test asset .14
7.4.3 Quality record report .14
7.4.4 Test completion report .15
7.4.5 Verification and validation report .15
7.4.6 Test status report .15
7.5 Summary of capabilities with characteristics .16
© ISO/IEC 2015 – All rights reserved PROOF/ÉPREUVE iii

ISO/IEC 30130:2015(E)
Annex A (informative) Capabilities mapping to test process .20
Annex B (informative) Overview of the approach for this International Standard .26
Bibliography .28
iv PROOF/ÉPREUVE © ISO/IEC 2015 – All rights reserved

ISO/IEC 30130:2015(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized 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 committees 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 procedures 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 rules 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 rights 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 explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 7, Software
and systems engineering.
© ISO/IEC 2015 – All rights reserved PROOF/ÉPREUVE v

ISO/IEC 30130:2015(E)
Introduction
This International Standard defines the framework to which capabilities of software testing tools are
allocated in order to identify the capabilities of products being used by any project for software testing.
To develop high-quality software with reasonable time and budget, the use of software testing tools is
required. The increase in the size and complexity of software is complemented by an increase in the
difficulty and complexity of software testing. This created a larger demand for the support of tools in
order to test software effectively and efficiently.
Testing tools are highly diverse due to their contexts of use. Testing itself varies by objective, such as
functional testing or nonfunctional testing, and granularity, such as unit testing or system testing.
Testing tool vendors vary by providing tools with a different function or combination of functions.
And despite vendor provided explanations for the type of testing support functions, there is little
common understanding of these functions. In this environment, it is difficult to utilize a testing tool
that is suitable for a project without common understanding of tool functions, proper acquisition of the
needed tools, and efficient training.
The framework defined by this In
...