Issue 15940: Test Maps (uml-testing-profile-rtf) Source: KnowGravity Inc. (Mr. Markus Schacher, markus.schacher(at)knowgravity.com) Nature: Enhancement Severity: Significant Summary: When identifying test cases one of the most important goals is to minimize the number of test cases while maximizing the test coverage. The core approach to achieve this is to employ various mechanism that facilitate reusability. Therefore, it is very helpful to visualize families of related test cases and their associations on dedicated diagrams. Resolution: Revised Text: Actions taken: January 12, 2011: received issue Discussion: A diagram for associating test cases in an early phase of a test process makes definitely sense and should be considered for one of the next minor revisions. Since test cases can be expressed as UML::Behavior, and UML::Behavior is a subclass of UML::Class, the most appropriate diagram would be a class diagram with additional symbols. In order to achieve this, it must be clearly and precisely states what concepts ans relationships are needed among test cases. Further more, definitions of monitors for test cases should be included; a test map may define behavioral description stating what should happen, if a monitored situation for a currently execute test case happens (write a log somewhere or interrupt the test case execution). The definition of such “behavioral” monitors must be aligned with issue 6956. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 12 Jan 2011 16:22:46 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Markus Schacher Employer: KnowGravity Inc. mailFrom: markus.schacher@knowgravity.com Terms_Agreement: I agree Specification: UML Testing Profile Section: 6.3.2 FormalNumber: 05-07-07 Version: 1.0 Doc_Year: 2005 Doc_Month: July Doc_Day: 07 Page: 14 Title: Test Maps Nature: Enhancement Severity: Significant CODE: 3TMw8 B1: Report Issue Description: When identifying test cases one of the most important goals is to minimize the number of test cases while maximizing the test coverage. The core approach to achieve this is to employ various mechanism that facilitate reusability. Therefore, it is very helpful to visualize families of related test cases and their associations on dedicated diagrams.