-
Key: UTP11-61
-
Legacy Issue Number: 15910
-
Status: closed
-
Source: Fraunhofer FOKUS ( Mr. Marc-Florian Wendland)
-
Summary:
Rational:
UTP spec, 1.0, section 6.3.1 TestArchitecture, subsection TestContext, subsubsection Description mentiones the following:
"A structured classifier acting as a grouping mechanism for a set of test cases. The composite structure of a test context is
referred to as test configuration. The classifier behavior of a test context is used for test control."Issue:
Since a test context extends UML::StructuredClassifier solely, a test context will never have a classifier behavior or operations, representing the test cases of that test context. StructuredClassifiers do not care about behavior but about structure. In order to be able to add a classifier behavior to a test context, it is required, that test context stereotypes only those classifiers that are subclasses of UML::StructuredClassifier AND UML::BehavioredClassifier (context TestContext inv: self.base_StructuredClassifier.oclIsKindOf(StructuredClassifier) and self.base_StructuredClassifier.oclIsKindOf(BehavioredClassifier).Even if in the current UML specification (haven't checked this thoroughly) all concrete subclasses of StructuredClassifier are subclasses of BehavioredClassifers, too, UTP should formally define this constraint since it is a crucial aspect of test context semantics
-
Reported: UTP 1.0 — Tue, 4 Jan 2011 05:00 GMT
-
Disposition: Resolved — UTP 1.1
-
Disposition Summary:
No Data Available
-
Updated: Sat, 7 Mar 2015 00:24 GMT
UTP11 — Test Context must be a UML::BehavioredClassifier, too
- Key: UTP11-61
- OMG Task Force: UML Testing Profile 1.1 (UTP) RTF