ISO/IEC 29119

Development of the set of ISO/IEC/IEEE 29119 software testing standards began in May 2007, based on existing standards such as the Institute of Electrical and Electronics Engineers's IEEE 829 (test documentation), and IEEE 1008 (unit testing); and the BSI Group's BS 7925-1 (vocabulary) and -2 (software components). At first the International Organization for Standardization (ISO) had no working group with significant software testing experience, so the ISO created WG26, which by 2011 was represented by more than 20 different countries. The actual fifth part of 29119 was published in November 2016 concerning the concept of keyword-driven testing, and revised in 2024. , the most recent versions of parts 1 to 5 are as follows: • ISO/IEC/IEEE 29119-5:2024, Part 5: Keyword-driven testing, published in December 2024 • ISO/IEC/IEEE 29119-3:2021, Part 3: Test documentation, published in October 2021 • ISO/IEC/IEEE 29119-2:2021, Part 2: Test processes, published in October 2021 • ISO/IEC/IEEE 29119-1:2022, Part 1: Concepts and definitions, published in January 2022 ==Structure and contents==

ISO/IEC/IEEE 29119-1:2022, Part 1: Concepts and definitions ISO/IEC/IEEE 29119 Part 1 facilitates the use of the other parts of the standard by introducing the vocabulary on which the standard is built and provides examples of its application in practice. The processes defined in this standard can be used in conjunction with different software development lifecycle models. Specification-based test design techniques These techniques are based on the (functional) specification of the system under test. They are also called black-box testing techniques. Suggested test design techniques in this group are: This standard is intended for users "who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords." ==Controversy==

Upon introduction of ISO/IEC/IEEE 29119, culminating in the summer of 2014, some software testers and associated organizations began making calls for the ISO to rescind the standard. Notable organizations that protested the standard included the Association for Software Testing Some reasons for opposition to the standard included: • lack of true consensus of content—as required by ISO/IEC—among professional testers though it's not clear if any further action by WG26 was taken due to software testers' complaints. ==References==