ISO/IEC/IEEE 29119 series consists of five standards. The goal is to set internationally agreed set of standards to support software testing.
Video ISO/IEC 29119
Introduction
​​â € <â €
The ISO/IEC/IEEE 29119 software testing standard is a set of internationally-defined documents that address software testing concepts, processes, techniques, documents, technologies, and terms.
Currently ISO/IEC/IEEE 29119 has five parts. The standard set uses a layered approach to define software testing, which is common to many ISO standards. This set of standards presents: the definition of tests and concepts (part 1); test process (part 2); test documentation (part 3); test technique (part 4); and keyword-based testing (part 5).
Jigsaw Standard
The ISO/IEC/IEEE 29119 standard is being developed by the Working Group 26 (WG26) Sub-Committee 7 (SC7) Joint Technical Committee 1 (JTC1) of the International Organization for Standardization (ISO) and the International Electrotechnical Commission in cooperation with the Software & Committee of Systems Engineering Standards from the Institute of Electrical and Electronic Engineers (IEEE) Computer Society.
In ISO/IEC JTC 1/SC 7, ISO/IEC/IEEE 29119 is part of a larger body of ISO/IEEE standards consisting of 153 standards, including the software life cycle process of ISO/IEC 12207 and ISO/IEC system engineering 15288.
WG26 members are experts and testers from within the international community of testers who participated and contributed the concept of testing during the design, review and consensus process. Participation is open to all; interested parties should approach their National Standards Board.
Development and Consensus
Development of ISO/IEC/IEEE 29119 standard software testing set was initiated in May 2007 by WG26; these standards are developed and developed by ISO and IEEE using their standard development methods. The process of development and approval is through consensus, which means that most standard development participants (not the entire world of software testing) agree with the document. Consensus is achieved with various countries and professional organizations that are members of SC7/JTC1 and IEEE: in ISO, SC7 member countries agree on ISO/IEC/IEEE 29119 by majority, while IEEE approves ISO/IEC/IEEE 29119 in its standard group association.
Membership in this is subject to ISO and IEEE rules and is an open process with these organizations, although not every tester in the world can be involved.
Consensus in ISO/IEEE does not mean that all testers in the world will agree with every idea and concept in the standard, but that organizations and people involved in standard production do reach agreement. Further, the consensus process does not imply that all new and viable concepts for developing or providing testing of goods and services are defined in the standards.
Publications
The first three sections are published in 2013, with the fourth and fifth following in 2015 and 2016 respectively:
- ISO/IEC/IEEE 29119-1: Drafts & amp; Definition , published in September 2013
- ISO/IEC/IEEE 29119-2: Testing Process , published September 2013
- ISO/IEC/IEEE 29119-3: Testing Documentation , published September 2013
- ISO/IEC/IEEE 29119-4: Test Techniques , published in December 2015
- ISO/IEC/IEEE 29119-5: Keyword Based Testing , published November 2016
Existing standard replacement
The ISO/IEC/IEEE 29119 standard replaces a number of existing software testing standards:
- IEEE 829 Test Documentation
- Unit Testing IEEE 1008
- BS 7925-1 Vocabulary Terms in Software Testing
- BS 7925-2 Standard Software Component Testing
These standards will be deleted over time.
BS 7925 was developed by the Working Standard Testing Party, sponsored by BCS SIGiST, and published by BSI in August 1998.
Maps ISO/IEC 29119
Destination and Usage
The ISO/IEC/IEEE 29119 software testing standard is intended to be an independent software, environment, and organization domain while supporting multiple life cycles and software methods. The process approach is fundamentally risk-based testing and can support test planning and strategy development.
Teams implementing the ISO/IEC/IEEE 29119 standard adopt and follow internationally recognized standards for software testing. This standard is available worldwide and thus provides the basis for international trading languages ​​within the scope of ISO and IEEE using organizations.
Desired benefits
They are not meant to be art or to capture all testing practices. New concepts and different testing practices will be added in future updates or new parts as ISO/IEC/IEEE 29119 evolves. Finally, the subsequent addition to the standard to address the concept and scope of other tests is likely, eg. model-based testing, etc.
Potential users of this standard may include:
- The company needs a common ground of testing concepts, terms and ideas (organizations for organizational trading languages ​​to help promote national and international businesses);
- Government organizations and regulators requiring ISO/IEC/ISO approved industry base line;
- Test organizations that require industry-based starting points;
- Buyers and software product providers to assess third parties;
- Software developers, e.g. to support unit level testing;
- The competent authorities wish to provide standard accreditation services;
- Developers and training providers of professional training;
- University lecturers want to teach their student content from the standard;
- University researchers seeking to research and collect data by standards;
- Software testers who want to apply the concept of the standard;
- Organizations that want to get standard accreditation.
Approach and tailoring
ISO/IEC/IEEE 29119-1 provides a common set of terms and concepts to support other parts. Basic approach to ISO/IEC/IEEE 29119-2 is risk-based. In risk-based testing, risk is used to limit and manage testing efforts in the context of problem space projects, costs and schedules. This is done to solve the problem that testing can be considered to have an infinite space problem (ie 100% complete testing is not possible). ISO/IEC/IEEE 29119-3 provides the definition of common test documents, which can be selected by customization as needed. ISO/IEC/IEEE 29119-4 provides structural and functional test techniques, which can also be selected as part of sewing activities. Finally, ISO/IEC/IEEE 29119-5 provides a definition of a keyword-based testing approach and concept, to be used in projects that require keywords. Using ISO 29119 heuristics, test issues can be managed and solved in the context of a project or organization. The use of standards can be customized (requirements removed, altered, or added) to support contracts or projects to fit local contexts and needs that result in different levels of adoption. For example, the user can select only 2 or 3 document outlines of ISO/IEC/IEEE 29119-3. According to common practice, adjustments must be approved by stakeholders.
Standard structure and content - Overview of each section
The following sections describe the parts of the current standard that are published and/or being developed.
ISO/IEC/IEEE 29119-1 (Part 1) - Concepts and Definitions
Software Testing ISO/IEC/IEEE 29119 - Concepts and Definitions, facilitates the use of other parts of the standard by introducing the vocabulary on which the standard is based and exemplifying its application in practice. Part 1 is informative, provides definitions, descriptions of software testing concepts and ways to implement software testing processes defined in ISO/IEC/IEEE 29119 part 2 standards and guidelines for other ISO/IEC/IEEE 29119 standards.
ISO/IEC/IEEE 29119-2 (Part 2) - Test Process
ISO/IEC/IEEE 29119 Software Testing - The Testing Process defines a generic process model for software testing intended for use by organizations when performing software testing. It consists of a description of the testing process that determines the software testing process at the organizational level, the level of test management and the dynamic test level. The processes defined in this standard can be used in conjunction with different software development life cycle models.
ISO/IEC/IEEE 29119-3 (Part 3) - Test Documentation
ISO/IEC/IEEE 29119 Software Testing - Test Documentation, including templates and sample test documentation generated during the testing process. The template supports the ISO/IEC/IEEE 29119-2 Test Process, that is by the testing process in which they are produced.
The documents defined in ISO/IEC/IEEE 29119-3 are as follows:
- Organization Testing Processing Documentation:
- - Test Policy
- - Organization Test Strategy
- Test Management Process Documentation:
- - Test Plan (including Test Strategy)
- - Test Status Report
- - Test Resolution Report
- Dynamic Testing Process Documentation:
- - Test Design Specs
- - Test Case Specification
- - Specification of Test Procedure
- - Test Data Terms
- - Test Data Readiness Report
- - Test Environment Requirements
- - Test Environment Readiness Report
- - Actual Results
- - Test Results
- - Test Execution Log
- - Incident Test Report
- - Test Data Readiness Report
ISO/IEC/IEEE 29119-4 (Part 4) - Test Technique
ISO/IEC/IEEE 29119 Software Testing - Test Technique, provides a standard definition of software design testing techniques (also known as test case design techniques or test methods) that can be used during the test design and implementation process defined in ISO/IEC/IEEE 29119-2. Engineering section 4 is intended to support part 2 or can be used without part 2.
Suggested Test Design Techniques are categorized in Specific Design-Based Design Techniques, Structured Design-Based Design Techniques, and Experimental Design Based Testing Techniques.
Specific Design-Based Test Techniques
Design-Based Design Techniques Specifications are based on the (functional) specifications of the system under test. They are also called black-box testing.
Recommended Design Scheme Techniques in this group are:
- Equality Partition
- Tree Treeing Method
- Value Limit Analysis
- Syntax Testing
- Combination Test Design Technique.
- Testing Decision Table
- Cause-Effects of Graphing
- Country Transition Testing
- Scenario Testing
- Random Testing
Structured Test Design Techniques
Design of Structured Test Techniques The structure is based on the (internal) structure of the system under test. They are also called white-box testing.
Recommended Design Scheme Techniques in this group are:
- Branch Testing
- Decision Testing
- Branch Condition Testing
- Branch Combination Testing
- Test Specific Condition Coverage (MCDC)
- Data Flow Test
Experience-Based Testing Techniques
Experimental Technique-Based Testing Techniques rely on the experience of human examiners.
Recommended Design Scheme Techniques in this group are:
- Error Guessing
ISO/IEC/IEEE 29119-5 (Part 5) - Keyword Based Testing
This standard includes keyword-based testing. Keyword-based testing is the approach to determine software testing (usually automated) that is already widely used in the software testing industry. This standard is intended for users who want to create keyword-based testing specifications, create appropriate frameworks, or build test automation based on keywords.
Future plans for standard maintenance
All ISO standards are reviewed, revised, and if necessary retired no later than 5 years after issuance. ISO/IEC/IEEE 29119 naturally follows the same process. Interested parties may provide input to standards for systematic review, either through ISO national standards bodies, or by directly approaching standards organizations including ISO, IEC or IEEE standard associations. The decision on standard revisions will be based on feedback, comments, feedback, consensus and voting available. Future plans for the ISO/IEC/IEEE 29119 section will seek to address many of the current problems and controversial items as consensus will allow. Impact and proof by using ISO/IEC/IEEE 29119 parts of fixed future work. Before the survival of standards can be determined, standards must be developed and available for use, which have occurred. This development illustrates what participants understand as a common practice in their experience in countries, companies, and organizations. These groups will become standard early users and will provide evidence of success or failure.
Controversy
There is resistance from parts of the testing community to the standardization of software testing. In particular, context-driven communities and the International Society for Software Testing reject this standard. In short, the reason for opposition is that ISO-29119 effectively excludes context-driven testing and, at the same time, context-based testing will not approve simple standards based on simple templates or formulas.
References
External links
- International Organization for Standardization
- BSI Group
- The UK Computer Society Specialist Interests Group in Software Testing
- ISO/IEC/IEEE 29119 Software Testing
- The International Society for Software Testing
- An open letter to the President of the International Organization for Standardization on ISO 29119
- Testing Standard Web site IEC 29119-1 "," IEC 29119-2 "," IEC 29119-3 "," IEC 29119-4 "," IEC 29119-5 "at the International Electrotechnical Commission
Source of the article : Wikipedia
0 Comments