UTP11 — Clarification of Arbiter Description

Rational: Arbiter is a predefined interface defining operations used for arbitration of tests. Test cases, test contexts, and the runtime system can use realizations of this interface to assign verdicts of tests and to retrieve the current verdict of a test (verdicts are discussed in Section 6.3.2, “Test Behavior,” on page 14)

Issue: Section 6.3.2 Test Behavior, Subsection Verdict mentions the following:
—
The final verdict of a test case is determined by an arbiter. Every test context has an arbiter and the tool vendor will provide a default arbiter if the test context does not explicitly specify one [… ]
—
Section 6.3.1 "TestArchitecture" (page 10) says:
—
Every test context must have an implementation of the arbiter interface, and the tool vendor constructing tools based on
the Testing Profile will provide a default arbiter to be used if one is not explicitly defined in the test context.
—

It seems to be a logical contradiction. Since the multiplictity of a test context's arbiter reference (see Fig. 6.1 TestArchitecture) is exactly one (so it has to be set in any case), why is it necessary to have a default arbiter in addition? It can never be used by a test context. In the case, a test context wants to use a kind of default arbiter, it has to define it anyway.
In order to avoid confusion on the readers, this must be clarified and probably simplified.

No Data Available