UTP2 2.0 FTF Avatar
  1. OMG Issue

UMLTP2 — TestLog.verdict should be extracted into a dedicated ArbitrationResult concept

  • Key: UMLTP2-27
  • Status: closed   Implementation work Blocked
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    UTP allows for capturing the most important test execution information for test cases and test sets. Those information are the minimum required information to document and reasoning over coverage of test requirements or test objectives.

    In theory and practice, it is possible and required to calculate verdicts by different verdict arbitrations for the very same test case or test set. A test log should only contain the mere information about the exchange of message between the test environment and the test item. Information about comparison or verdict arbitration should not be part of a test log, but of a dedicated ArbitrationResult concept.

    The extraction of verdict into a dedicated ArbitrationResult is also necessary to avoid introducing redundant information into the model by copying the test log elements for the mere purpose of verdict association. Currently, it would not introduce much redundancy by copying just a single TestLog element (and the respective stereotype, of courde), but it is expected that UTP will introduce a fine-grained log model in a future version that is capable of recording all relevant information of test executions. If verdict still remained to test log or the test log entries later on, it would be necessary to potentially copy entire (and long) test log information with dozens of actual procedural elements, just for the sake of additional verdict arbitration. This situation would not scale at all for large test projects.

  • Reported: UTP 2.0b1 — Tue, 23 Jan 2018 20:11 GMT
  • Disposition: Resolved — UTP2 2.0
  • Disposition Summary:

    ArbitrationResult is an important concept to avoid redundancy

    The concept ArbitrationResult will be integrated into the Profile Specification to avoid redundancy in case the very same test case shall be checked by different ArbitrationSpecifications which may produce different verdicts.
    No change of the conceptual model required, for the ArbitrationResult is simply a technical solution to avaoid redundancy, not a conceptual change.
    The solution will be based on UML's InstanceSpecification concept, for an ArbitrationResult is actually an instance of the execution of an ArbitrationSpecification.
    ArbitrationResult will contain at least the attribute ‘verdict’. Additional information might be added by means of the pre-defined auxiliary library (later on)

  • Updated: Wed, 3 Oct 2018 14:16 GMT
  • Attachments: