1. OMG Mailing List
  2. UML Testing Profile 2 (UTP) mailing list

Open Issues

  • Issues not resolved
  • Name: utp2-ftf
  • Issues Count: 16

Issues Descriptions

The definitions of test level and test type are useless/not understandable.

  • Key: UMLTP2-7
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    This issue was raised by Manfred Koethe as UTP 2 revised submission reviewer.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 09:08 GMT
  • Updated: Wed, 17 Jan 2018 10:32 GMT

Predefined verdict fault has no meaning

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

    The predefined verdict fault and error are synonyms. Fault shall be removed. Error is more common in the test automation community to describe situations where some technical exception occured in the test environment.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 13:13 GMT
  • Updated: Wed, 17 Jan 2018 09:19 GMT

Predefined verdicts are not always reusable

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

    UTP 2 provides the predefined verdict instances none, pass, inconclusive, fail, error. These instances are currenty represented by LiteralStrings of type 'verdict'. Using LiteralStrings is fine for the UTP test logging facility for TestCaseLog and TestSetLog simply refers to ValueSpecifications of type 'verdict'. But in situations where those predefined verdict instances shall be used in a different context e.g. in the context of types of Properties of a StructuredClassifier and InstanceSpecifications thereof, LiteralStrings cannot be really reused for Slot values. Therefore, the LiteralString should be reworked into InstanceSpecifications of type 'verdict' with their specification set to LiteralStrings (of type 'verdict') with name and value set to the 5 predefined verdicts.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 13:10 GMT
  • Updated: Wed, 17 Jan 2018 09:19 GMT

The definitions of test level and test type are useless/not understandable.

  • Key: UMLTP2-6
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    This issue has been raised by Manfred Koethe as UTP 2 revised submission reviewer.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 09:07 GMT
  • Updated: Wed, 17 Jan 2018 08:28 GMT

Some references to "UTP" in the description in the Profile Specification need to be cleaned-up.

  • Key: UMLTP2-9
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    This issues was raised by Manfred Koethe as UTP 2 revised submission reviewer

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 09:14 GMT
  • Updated: Wed, 17 Jan 2018 08:20 GMT

OCL code and natural language description of Constraints inconsistent

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

    Many Constraints of stereotypes are inconsistent with respect to OCL and natural language.

    See section 8.5.1.2.2 TestCase:

    • Constraint 'Use of BehavioredClassifier' is inconsistent
    • Constraint /* DRTC02: It is necessary that each test execution schedule requires at most one preconditon. */ does not belong to the stereotype test case at all.

    This is the case for most of the Constraints in section 8. A thorough check would be required to clean that up.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 15:35 GMT
  • Updated: Tue, 16 Jan 2018 16:08 GMT

Arbitration Specification Semantics

  • Key: UMLTP2-13
  • Status: open  
  • Source: KnowGravity Inc. ( Markus Schacher)
  • Summary:

    The relationship between "8.7.1 Arbitration Specifications" and "9.3 UTP Arbitration" is not clear. Probably, 9.3 is only the (informal?) semantics of 8.7.1?

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 12:52 GMT
  • Updated: Tue, 16 Jan 2018 16:07 GMT

Non-unique Rule Identifier

  • Key: UMLTP2-12
  • Status: open  
  • Source: KnowGravity Inc. ( Markus Schacher)
  • Summary:

    Rules DRTC01 (should be "DRTR01") and DRTC01 have the same identifier.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 10:32 GMT
  • Updated: Tue, 16 Jan 2018 16:06 GMT

Clarification of vocabularies

  • Key: UMLTP2-11
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    UTP should better distinguish the origin of the terms in the vocabulary. E.g., there are concepts and definitions, which are solely listed in the conceptual model or the profile implementation vice versa. The UTP vocabulary should indicate where this term originated from.

    A potential solution is to add a introductory sentence to section 4 to explain that the terms in section 4 are a summary of the conceptual model of UTP 2 (section 7). Furthermore, improve section 6.2 (Typographical Conventions) with respect to the kids of cross references in the spec (to the definition, to the conceptual model to stereotypes)

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 09:46 GMT
  • Updated: Tue, 16 Jan 2018 16:06 GMT

LoginExample is not in synch with latest Profile Specification

  • Key: UMLTP2-10
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    Double-check that the LoginExample copes with the latest version of the spec.

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 09:17 GMT
  • Updated: Tue, 16 Jan 2018 16:05 GMT

Some references to "UML 2.5" in the constraints in the Profile Specification need to be cleaned-up.

  • Key: UMLTP2-8
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    This issue was raised by Manfred Koethe as UTP 2 revised submission reviewer

  • Reported: UTP 2.0b1 — Tue, 16 Jan 2018 09:13 GMT
  • Updated: Tue, 16 Jan 2018 16:05 GMT

Formal specification of ComplementedValue incomplete

  • Key: UMLTP2-5
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    The last two paragraphs represents an incomplete formal specification of the semantics of ComplementedValue. It should be removed for does not have an added value in the current state.

  • Reported: UTP 2.0b1 — Mon, 15 Jan 2018 15:50 GMT
  • Updated: Tue, 16 Jan 2018 16:03 GMT

Invalid links

  • Key: UMLTP2-4
  • Status: open  
  • Source: KnowGravity Inc. ( Markus Schacher)
  • Summary:

    Most of the intra-document links (the blue underlined words) do not refer to the correct target. This seems to be caused by the transformation process between the original specification model generated out of the model and the final PDF document published as the beta version of UTP.

  • Reported: UTP 2.0b1 — Mon, 15 Jan 2018 14:03 GMT
  • Updated: Tue, 16 Jan 2018 16:03 GMT

Formal specification of ChoiceOfValues incomplete

  • Key: UMLTP2-3
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    The formal specification of ChoiceOfValues is incomplete. These paragraphs are relics from an approach to provide a precise semantics of data value extensions.

    Suggestion: Remove these paragraphs.

  • Reported: UTP 2.0a1 — Mon, 15 Jan 2018 13:42 GMT
  • Updated: Tue, 16 Jan 2018 16:02 GMT

Clean-up description of AnyValue

  • Key: UMLTP2-2
  • Status: open  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    The last two paragraphs of AnyValue description are incomplete.

    Suggest resolution: Remove those two paragraphs

  • Reported: UTP 2.0a1 — Mon, 15 Jan 2018 13:25 GMT
  • Updated: Tue, 16 Jan 2018 16:01 GMT

Include changes specified by errata

  • Key: UMLTP2-1
  • Status: open  
  • Source: KnowGravity Inc. ( Markus Schacher)
  • Summary:

    Most changes specified in the errata to the beta specification (ad/17-06-01) have not yet been included (except for the changes on the cover page). These changes must be included in the final specification.

  • Reported: UTP 2.0b1 — Mon, 15 Jan 2018 11:45 GMT
  • Updated: Tue, 16 Jan 2018 16:01 GMT