Changes between Version 25 and Version 26 of path:pathMap

Timestamp:

12/13/2013 12:03:59 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathMap

@@ -58 +58 @@
  Tree map (middle):: Represents a structural system overview and its relation to test execution. This visualization represents categories/packages as columns and their classes as rows. Each class represents each of its methods as a box. In addition to it, methods are optionally ordered in columns with respect to their method category. The allocated space is proportional to the number of methods per node. Packages, classes, and methods are sorted alphabetically and for a clear separation we distinguish between test classes on the left-hand side and application classes on the right-hand side. Developers can systematically explore the visualization and interactively obtain more details about specific method boxes such as its name and covering tests. Moreover, each method can be colored with a hue element for reflecting specific analysis metrics. In addition to that, the visualization colors a test method in green, yellow, or red if the test respectively succeeds or fails.
 
- Interactive elements on tree map (morphs):: Each small rectangle morph represents a method of the system under observation. Method with an ''u'' mark unit test methods.  By interactively hovering over the visualization, labels present the current selected source code entity. With a click on a box the following buttons can appear.
- * [[Image(pathMapMorphButton1.png)]] The standard buttons that are mostly available at each method. ''Browse'' opens a source code browser for this specific method ('''Note:''' If a coverage analysis has been chosen (test quality or fault localization flap), this will also refine the coverage results at the statement-level. The browser underlines the corresponding statements). ''Information'' open a new dialog that shows additional data about the computed analysis metrics (color in the method). ''Rerun'' allows developers to rerun one specific test case only. This button is only available for unit test methods (''u'' mark). ''Debug'' sets a breakpoint in the chosen method and runs a specific test that covers this method. Thus, a symbolic debugger opens at the chosen method and allows developers to explore its run-time behavior. ''Pathfinder'' opens with the last button our lightweight back-in-time debugger at the chosen method. This allows developers to explore the entire execution history of a specific test that the chosen method is involved. 
+ Interactive elements on tree map (morphs):: Each small rectangle morph represents a method of the system under observation. Methods with a ''u'' mark unit test methods. By interactively hovering over the visualization, labels present the current selected source code entity. With a click on a box the following buttons can appear on a method.
+ * [[Image(pathMapMorphButton1.png)]] The standard buttons that are mostly available. ''Browse'' opens a source code browser for this specific method ('''Note:''' If a coverage analysis has been chosen (test quality or fault localization flap), this will also refine the coverage results at the statement-level. The browser underlines the corresponding statements). ''Information'' opens a new dialog that shows additional data about the computed analysis metrics (color in the method). ''Rerun'' allows developers to rerun one specific test case. This button is only available for unit test methods (''u'' mark). ''Debug'' sets a breakpoint in the chosen method and runs a specific test that covers this method. Thus, a symbolic debugger opens at the chosen method and allows developers to explore its run-time behavior. ''Pathfinder'' opens our lightweight back-in-time debugger at the chosen method. This allows developers to explore the entire execution history of a specific test case that the chosen method is involved. 
  * [[Image(pathMapMorphButton2.png)]] If contracts are available and a specific method includes violations, this button allows developers to further inspect the violated assertions. The same icon highlights methods in the tree map, if violations have been occurred. 
  * [[Image(pathMapMorphButton3.png)]] If the tree map has not enough space for displaying all methods, it automatically summarizes them into their classes. Only a large rectangle is available that can be further explored at the method level with this button. 
-
 
  Text box (bottom):: Summarizes some static project metrics such as number of classes and methods or lines of code (LoC).