Programutveckling och systemdokumentation
- +Ämnesområden
- +Informationsteknik, kontorsutrustning (17)
- Informationsteknik: allmänt (3)
- IT-säkerhet (0)
- +Kodning av information (5)
- Programspråk (1)
- Programutveckling och systemdokumentation (2)
- +Öppna system (OSI) (0)
- Nätarkitekturer (0)
- Datorgrafik (0)
- Mikroprocessorsystem (0)
- Terminalutrustning och övrig kringutrustning (0)
- Gränssnitt och anslutningsutrustning (0)
- Molnbaserade datortjänster (0)
- +Datalagringsmedier (0)
- +IT-tillämpningar (6)
- Kontorsutrustning (0)
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.
This standard specifies a set of definitions, rules, and steps for applying a non-functional size measurement method and provides guideline and examples of how to use the size measurements in software projects