International

ISO/IEC/IEEE 29119-5:2016

31 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

31 controls 0 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1-4Scope, normative references and terms0
2Claiming full or tailored conformance0
5Keyword-driven testing concepts: layers, types of keywords, keywords and data0
6.1Overview of applying keyword-driven testing0
6.2Identify and document keywords0
6.3Compose keyword-driven test cases0
6.4Combine keywords with data-driven testing0
6.5Keep keywords modular and refactor them0
6.6Apply keyword-driven testing within the test design process (TD1 to TD6)0
6.7Convert existing test cases to keyword-driven test cases0
7.1-7.2Framework overview and the components: keyword editor, decomposer and data sequencer, the manual test assistant, the tool bridge, execution engine, keyword library, data and script0
7.2.1Provide the framework components needed for manual and automated execution0
7.3.2Document keywords and their parameters0
7.3.3Editor: display, author and reference keywords0
7.3.4Decomposer and data sequencer handle parameters0
7.3.5Manual test assistant guides manual execution0
7.3.6Tool bridge supplies execution code0
7.3.7Execution engine: sequential execution, results, logging and error handling0
7.3.8Keyword library supports keyword definition0
7.3.9Script repository stores and references scripts0
7.4.10Version the execution code0
7.4.2Document the rules for authoring keywords0
7.4.3Editor: syntax checking, tracking, guidance and versioning0
7.4.4Build keywords and structured data0
7.4.5Attach outputs to the test log0
7.4.7Execution engine: data access, blocked keywords, data-driven runs, parameter matching and loop limits0
7.4.8Keyword library: composite keywords, versioning and aliasing0
7.4.9Version the test data0
8Exchange keyword-driven test data through a recognised standard0
AKeyword naming and description conventions (Annex A, normative)0
B-FAnnexes B to F (informative): benefits and issues, getting started, roles and tasks, basic keywords, examples0

Tell me when ISO/IEC/IEEE 29119-5:2016 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for ISO/IEC/IEEE 29119-5:2016, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition