Changes between Version 40 and Version 41 of path:pathMap

Timestamp:

12/13/2013 04:43:55 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathMap

@@ -59 +59 @@
 
  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(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. [wiki:path:pathFinder ''Pathfinder''] opens our [wiki:path:tutorial:backintime 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.