Working Group Details
SF - Working Group for Software Testing
|IEEE Program Manager|
P29119-1 - ISO/IEC/IEEE International Standard - Software and systems engineering --Software testing --Part 1:Concepts and definitions
This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
IEEE/ISO/IEC P29119-2 - ISO/IEC/IEEE Draft International Standard - Software and systems engineering - Software testing -- Part 2: Test processes
This part of ISO/IEC/IEEE 29119 specifies test processes that can be used to govern, manage and implement software testing for any organization, project or smaller testing activity. It comprises generic test process descriptions that define the software testing processes. Supporting informative diagrams describing the processes are also provided. This part of ISO/IEC/IEEE 29119 is applicable to testing in all software development lifecycle models. This part of ISO/IEC/IEEE 29119 is intended for, but not limited to, testers, test managers, developers and project managers, particularly those responsible for governing, managing and implementing software testing
IEEE/ISO/IEC P29119-4 - IEEE/ISO/IEC Draft International Standard - Software and systems engineering--Software testing--Part 4: Test techniques
The purpose of this part of ISO/IEC/IEEE 29119 is to provide an International 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 describe a process for test design and implementation; instead, it describes a set of techniques that can be used within the test design and implementation process defined in 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 can be used to derive test cases that, when executed, generate evidence that test item requirements have been met 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 specific (risk-based testing is covered in ISO/IEC/IEEE 29119-1 and ISO/IEC/IEEE 29119-2).
IEEE/ISO/IEC 29119-5-2016 - ISO/IEC/IEEE International Standard - Software and systems engineering -- Software testing -- Part 5: Keyword-Driven Testing
This part of ISO/IEC/IEEE 29119 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 test engineers to share their work items, such as test cases, test data, keywords, or complete test specifications; - defining minimum requirements for tools, which are necessary to fully utilize keyword-driven testing. These requirements could apply to any tools which support 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 giving advice when to use hierarchical keywords, when to use "flat" structured keywords, and describe specific types of keywords (e.g. keywords for navigation or for checking something); - providing an initial list of suggested 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 composed to create business level keywords as required. This standard is applicable for all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.