Changes between Version 22 and Version 23 of path:pathMap

Timestamp:

12/13/2013 11:44:17 AM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathMap

@@ -14 +14 @@
 We derive type data from the concrete objects used during test case executions and provide developers this hidden information to assist in navigating source code and using application programming interfaces (APIs) correctly.
 By making this hidden test knowledge available, developers have additional information for debugging, testing, and understanding their programs. 
-
 
 !PathMap is our extended test runner that reveals the hidden knowledge of test cases and presents it to developers.  
@@ -55 +54 @@
  * ''Run Errors:'' Executes only (red) tests that have an error before. Analysis depends on opened flaps. 
 
- Text box (top)::
+ Text box (top):: Summarizes test results (passed, failed, errors, and expectations) as usual. 
 
- Tree map (middle)::
+ 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 about the visualization, labels present the current selected source code entity. With a click on a box the following buttons can appear.
 
-
-
-each morph a method -- u for unit test
-
-
-
- Interactive elements on tree map (morphs)::
-
-labels