iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO/IEC/IEEE 29119-5:2016

(Main)

Software and systems engineering — Software testing — Part 5: Keyword-Driven Testing

Software and systems engineering — Software testing — Part 5: Keyword-Driven Testing

ISO/IEC/IEEE 29119-5:2016 defines an efficient and consistent solution for Keyword-Driven Testing by: giving an introduction to Keyword-Driven Testing; providing a reference approach to implement Keyword-Driven Testing; defining requirements on frameworks for Keyword-Driven Testing to enable testers to share their work items, such as test cases, test data, keywords, or complete test specifications; defining requirements for tools that support Keyword-Driven Testing. These requirements could apply to any tool that supports the Keyword-Driven approach (e.g., test automation, test design and test management tools); defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results); defining levels of hierarchical keywords, and advising use of hierarchical keywords. This includes describing specific types of keywords (e.g. keywords for navigation or for checking a value) and when to use "flat" structured keywords; providing an initial list of example generic technical (low-level) keywords, such as "inputData" or "checkValue". These keywords can be used to specify test cases on a technical level, and may be combined to create business-level keywords as required. NOTE This standard is applicable to all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.

Ingénierie du logiciel et des systèmes — Essais du logiciel — Partie 5: Essais axés sur des mots-clés

General Information

Status
Published
Publication Date
16-Nov-2016
ICS
35.080 - Software
Technical Committee
ISO/IEC JTC 1/SC 7 - Software and systems engineering
Drafting Committee
ISO/IEC JTC 1/SC 7/WG 26 - Software testing
Current Stage
Ref Project

Relations

Consolidated By
ISO 6887-5:2020 - Microbiology of the food chain — Preparation of test samples, initial suspension and decimal dilutions for microbiological examination — Part 5: Specific rules for the preparation of milk and milk products
Effective Date
06-Jun-2022

Buy Standard

ISO/IEC/IEEE 29119-5:2016 - Software and systems engineering -- Software testingISO/IEC/IEEE 29119-5:2016 - Software and systems engineering -- Software testing
PreviousNext
Standard
ISO/IEC/IEEE 29119-5:2016 - Software and systems engineering -- Software testing
English language
54 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO/IEC/
STANDARD IEEE
29119-5
First edition
2016-11-15
Software and systems engineering —
Software testing —
Part 5:
Keyword-Driven Testing
Ingénierie du logiciel et des systèmes — Essais du logiciel —
Partie 5: Essais axés sur des mots-clés
Reference number
©
ISO/IEC 2016
©
IEEE 2016
© ISO/IEC 2016, Published in Switzerland
© IEEE 2016
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 IEC Central Office 3,
Institute of Electrical and Electronics Engineers, Inc
Ch. de Blandonnet 8 • CP 401
rue de Varembé CH- 3 Park Avenue, New York
CH-1214 Vernier, Geneva, Switzerland
NY 10016-5997, USA
1211 Geneva 20
Tel. +41 22 749 01 11
Switzerland
Fax +41 22 749 09 47
E-mail inmail@iec.ch
copyright@iso.org
stds.ipr@ieee.org
Web www.iec.ch
www.iso.org
www.ieee.org
© ISO/IEC 2016 – All rights reserved
ii © IEEE 2016 – All rights reserved

Contents Page
1 Scope .1
2 Conformance .1
2.1 Intended usage .1
2.2 Full conformance .1
2.3 Tailored conformance .2
3 Normative references .2
4 Terms and definitions .2
5 Introduction to Keyword-Driven Testing .4
5.1 Overview .4
5.2 Layers in Keyword-Driven Testing .7
5.2.1 Overview .7
5.2.2 Domain layer .8
5.2.3 Test interface layer .9
5.2.4 Multiple layers .9
5.3 Types of keywords. 10
5.3.1 Simple keywords. 10
5.3.2 Composite keywords . 11
5.3.3 Navigation/interaction (input) and verification (output) . 14
5.3.4 Keywords and test result . 14
5.4 Keywords and Data. 15
6 Application of Keyword-Driven Testing . 16
6.1 Overview . 16
6.2 Identifying keywords . 16
6.3 Composing test cases . 17
6.4 Keywords and data-driven testing . 18
6.5 Modularity and refactoring . 18
6.6 Keyword-Driven Testing in the Test Design Process . 19
6.6.1 Overview . 19
6.6.2 TD1 Identify Feature Sets . 20
6.6.3 TD2 Derive Test Conditions . 20
6.6.4 TD3 Derive Test Coverage Items . 20
6.6.5 TD4 Derive Test Cases . 21
6.6.6 TD5 Assemble Test Sets . 22
6.6.7 TD6 Derive Test Procedures . 22
6.7 Converting non keyword-driven test cases into Keyword-Driven Testing . 22
7 Keyword-Driven Testing Frameworks . 22
7.1 Overview . 22
7.2 Components of a Keyword-Driven Testing framework. 23
7.2.1 Overview . 23
7.2.2 Keyword-driven Editor . 25
7.2.3 Decomposer . 26
7.2.4 Data sequencer . 26
7.2.5 Manual test assistant . 26
7.2.6 Tool bridge . 26
7.2.7 Test execution environment and execution engine . 26
7.2.8 Keyword library . 27
7.2.9 Data . 27
7.2.10 Script repository . 27
7.3 Basic attributes of the Keyword-Driven Testing framework . 27
7.3.1 General information on basic attributes . 27
7.3.2 General attributes . 27
7.3.3 Dedicated keyword-driven editor (tool) . 28
7.3.4 Decomposer and data sequencer . 29
© ISO/IEC 2016 – All rights reserved iii
© IEEE 2016 – All rights reserved

7.3.5 Manual test assistant (tool) . 29
7.3.6 Tool bridge . 29
7.3.7 Test execution engine . 29
7.3.8 Keyword library . 30
7.3.9 Script repository . 30
7.4 Advanced attributes of frameworks . 30
7.4.1 General information on advanced attributes . 30
7.4.2 General attributes . 30
7.4.3 Dedicated keyword-driven editor (tool) . 31
7.4.4 Decomposer and data sequencer . 31
7.4.5 Manual test assistant . 31
7.4.6 Tool bridge . 31
7.4.7 Test execution environment and execution engine . 32
7.4.8 Keyword library . 33
7.4.9 Test data support . 33
7.4.10 Script repository . 33
8 Data interchange . 33
Annex A (normative) Conventions . 34
Annex B (informative) Benefits and Issues of Keyword-Driven Testing . 35
B.1 General benefits of Keyword-Driven Testing . 35
B.2 Benefits of Keyword-Driven Testing for test automation . 35
B.3 Benefits of Keyword-Driven Testing for manual testing . 36
B.4 Possible issues with Keyword-Driven Testing . 36
Annex C (informative) Getting started with Keyword-Driven Testing . 37
C.1 General . 37
C.2 Identifying Keywords . 37
C.3 Composing test cases . 38
Annex D (informative) Roles and Tasks . 39
D.1 Overview – Roles and Tasks . 39
D.2 Domain expert . 39
D.3 Test designer . 39
D.4 Test automation expert . 40
Annex E (informative) Basic keywords . 41
E.1 Overview . 41
E.2 Basic keywords for a GUI . 41
E.3 Example application of basic keywords . 45
Annex F (informative) Examples. 49
F.1 Overview .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO/IEC 24773-2:2024(Main)
Software and systems engineering — Certification of software and systems engineering professionals — Part 2: Guidance regarding description of knowledge, skills, and competencies contained in schemes

This document contains guidance for certification that can be used by certification or qualification bodies regarding the description of knowledge, skill and competence within their particular schemes based on ISO/IEC 24773-1.

  • Standard
    21 pages
    English language
    sale 15% off
ISO
ISO/IEC 29110-1-1:2024(Main)
Systems and software engineering — Lifecycle profiles for very small entities (VSEs) — Part 1-1: Overview

This document establishes the major concepts required to understand and use the ISO/IEC 29110 series. It specifies the characteristics and requirements of a VSE, and clarifies the rationale for VSE-specific profiles, documents, profile specifications and guidelines. This document introduces the taxonomy (catalogue) of ISO/IEC 29110 profiles and the ISO/IEC 29110 series. This document is applicable to a VSE but can also be used by an entity that is larger than a VSE.

  • Standard
    14 pages
    English language
    sale 15% off
ISO
ISO/IEC 29110-1-2:2024(Main)
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1-2: Vocabulary

This document defines the terms common to the ISO/IEC 29110 series. This document is applicable to very small entities (VSEs), and their customers, assessors, standards producers, tool vendors and methodology vendors.

  • Standard
    18 pages
    English language
    sale 15% off
ISO
ISO/IEC/IEEE 24748-1:2024(Main)
Systems and software engineering — Life cycle management — Part 1: Guidelines for life cycle management

This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: — addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; — establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services; — defines the concept of a life cycle; — supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; — provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; — describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects); — shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; — describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.

  • Standard
    76 pages
    English language
    sale 15% off
ISO
ISO/IEC/IEEE 24748-2:2024(Main)
Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (system life cycle processes)

The proposed project is a revision of ISO/IEC/IEEE 24748-2:2018, Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (System life cycle processes). There are no scope changes. ISO/IEC/IEEE 24748-2 is a guideline for the application of ISO/IEC/IEEE 15288. It addresses system, life cycle, organizational, project, and process, concept application, principally through reference to ISO/IEC/IEEE 24748-1 and ISO/IEC/IEEE 15288. It gives guidance on applying ISO/IEC/IEEE 15288 from the aspects of strategy, planning, application in organizations, and application on projects. It also provides comparison of the differences between ISO/IEC/IEEE 15288 current revision and the prior version, ISO/IEC 15288:2015.

  • Standard
    63 pages
    English language
    sale 15% off
ISO
ISO/IEC 25002:2024(Main)
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality model overview and usage

This document establishes a framework for defining quality models which are composed of quality characteristics and sub-characteristics. In particular, this document provides: — the concept of a quality model; — the structure and semantics of quality models; — the relationship between quality models and the other concepts, including measurement, requirement definition, and evaluation; — guidelines, requirements and examples for using quality models.

  • Standard
    17 pages
    English language
    sale 15% off
ISO
ISO/IEC 19770-1:2017/Amd 1:2024(Amendment)
Information technology — IT asset management — Part 1: IT asset management systems — Requirements — Amendment 1: Climate action changes
  • Standard
    1 page
    English language
    sale 15% off
ISO
ISO/IEC 19770-6:2024(Main)
Information technology — IT asset management — Part 6: Hardware identification tag

This document provides specifications for a transport format which enables the digital encapsulation of this data. This document refers to an encapsulation of hardware identification (HWID) data as a HWID tag, just as ISO/IEC 19770-2 refers to software identification (SWID) tags for software identification. This document applies to the following. — Tag producers: organizations that create HWID tags for use by others in the market. A tag producer can be part of the organization creating the hardware or a third-party organization. These organizations can be broken down into two major categories. — Device or component providers: entities responsible for the manufacturing or creation of the hardware device and/or associated operating system, virtual environment, or application platform. Platform providers which support this document can additionally provide tag management capabilities at the level of the platform or operating system. — Tag tool providers: entities that provide tools to create hardware identification tags. For example, tools within development environments that generate hardware identification tags, or installation tools that can create tags on behalf of the installation process, and/or desktop management tools that can create tags for underlying hardware, virtual machines, or platforms that did not originally have a hardware identification tag. — Tag consumers: tools and/or organizations who utilize information from HWID tags are broken down into the following two major categories. — Device or component consumers: entities that purchase, install, integrate, and/or otherwise deploy physical or virtual hardware or components. — IT discovery and processing tool providers: entities that provide tools to collect, store, and process hardware identification tags. These tools may be targeted at a variety of different market segments, including security, asset management, and logistics. This document deals only with hardware device or component identification. This document does not detail information technology asset management (ITAM) processes required for discovery and management of hardware (which is provided in ISO/IEC 19770-1) software identification tags (as defined by ISO/IEC 19770-2), entitlement tags (as defined by ISO/IEC 19770-3), or resource utilization measurements (as defined by ISO/IEC 19770-4).

  • Standard
    41 pages
    English language
    sale 15% off
ISO
ISO/IEC 25019:2023(Main)
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality-in-use model

This document defines a quality-in-use model composed of three characteristics (which are further subdivided into sub-characteristics) that can influence stakeholders when products or systems are used in a specified context of use. This model is applicable to the entire spectrum of information system and IT service system, including both computer systems in use and software products in use. This document provides a set of quality characteristics for specifying, measuring, evaluating and improving quality-in-use. In this document, because context of use is specified as prerequisite of quality-in-use, context of use is necessary to be re-specified to change prerequisite when a product or service intend to fulfil to context of use changes. The model can be applied, in particular, by those responsible for specifying and evaluating software product quality, such as developers, acquirers, quality assurance and control staff, and independent evaluators. Activities during product development that can benefit from the use of the quality model can include, but are not limited to: — identifying requirements for information system and IT service system in use; — validating the comprehensiveness of a quality-in-use requirements specification; — identifying information system and IT service system design objectives for quality-in-use; — identifying quality-in-use control criteria as part of overall quality assurance; — identifying acceptance criteria for information system and IT service system or information systems; — establishing measures to address the consequences of using products in specified context-of -use; — presenting evaluation items for ethics considerations when using information system and IT service system; — supporting governance of digitalization activities.

  • Standard
    31 pages
    English language
    sale 15% off
ISO
ISO/IEC 25010:2023(Main)
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Product quality model

This document defines a product quality model, which is applicable to ICT (information and communication technology) products and software products. The product quality model is composed of nine characteristics (which are further subdivided into subcharacteristics) that relate to quality properties of the products. The characteristics and subcharacteristics provide a reference model for the quality of the products to be specified, measured and evaluated. NOTE 1 In this document, a product refers to an ICT product that is part of an information system. ICT product components include subsystems, software, firmware, hardware, data, communication infrastructure, and other elements that are part of the ICT product. This model can be used for requirements specification and evaluation of the target products’ quality throughout their lifecycle by several stakeholders, including developers, acquirers, quality assurance and control staff and independent evaluators. Activities in the product lifecycle that can benefit from the use of this model include: — eliciting and defining product and information system requirements; — validating the comprehensiveness of requirements definition; — identifying product and information system design objectives, and design necessary process for achieving quality; — identifying product and information system testing objectives; — identifying quality control criteria as the part of quality assurance; — identifying acceptance criteria for a product and/or an information system; — establishing measures of product quality characteristics in support of these activities. NOTE 2 Usage of the quality model for measurement is explained in Annex C.

  • Standard
    22 pages
    English language
    sale 15% off