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.
- Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More About C/S2ESC - Software & Systems Engineering Standards Committee - Status
- Active PAR
- PAR Approval
- 2022-09-21
- Superseding
- 29119-5-2016
Working Group Details
- Society
- IEEE Computer Society
Learn More About IEEE Computer Society - Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More About C/S2ESC - Software & Systems Engineering Standards Committee - Working Group
-
SF - Working Group for Software Testing
- IEEE Program Manager
- Patricia Roder
Contact Patricia Roder - Working Group Chair
- Jon Hagar
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
P23612
Software and systems engineering -- Incident management
This document defines an incident management process and supporting documentation that can be used to manage and implement incident management within any organization, project or maintenance activity. Supporting informative diagrams describing the process and example documents are also provided. This standard is applicable to incident management in all life cycle models. It discusses the relationship of incident management to problem management and can be applied to security incident management.
P3407
Standard for End-to-End Software Testing Automation Tools
This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
No Active Standards
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
No Superseded Standards
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards