Changes between Version 36 and Version 37 of path:pathMap

Timestamp:

12/13/2013 04:17:40 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathMap

@@ -91 +91 @@
 [[Image(profilingFlap.png)]]
 
- ''Method Calls'' drop down list (top):: Choose the profiling measurement. We offer number of method calls, number of created instances, pure run-time, and run-time per method call. 
+ ''Method Calls'' drop down list (top):: Choose the profiling measurement. We offer number of method calls, number of created instances (in this case, the tree map hides all methods and limits the visualization to classes), pure run-time, and run-time per method call. 
 
- ''Profile Leafs'' button:: With this option, we measure the exact run-time of each method for its own (ignoring the run-time of sub-calls). This means the sum of all called methods equals to the entire run-time. Without this option, we measure for each method entry and exit so that sub-calls to following methods are also included in the results. 
+ ''Profile Leafs'' button:: With this option, we measure the exact run-time of each method for its own (ignoring the run-time of sub-calls). This means the sum of all called methods equals to the entire run-time. Without this option, we measure for each method its entry and exit so that following method calls are also included in the results. 
 
- Color legend:: Shows the spectrum from blue as less performance to red as high performance requirements. 
+ Color legend:: Shows the required performance spectrum from blue as less to red as high. 
 
  ''Highscore'' button:: Shows a sorted list of all performance measurements. 
@@ -107 +107 @@
 [[Image(faultLocalizationFlap.png)]]
 
- ''Ochiai'' drop down list (top)::
+ ''Ochiai'' drop down list (top):: Choose a ''spectrum-based fault localization'' metric. We have implemented Ochiai, Tarantula, and Jaccard. Nevertheless, Ochiai has been shown to be the best choice in most cases. So, this metric is a proper default value. 
 
- Color legend::
+ Color legend:: Shows the failure cause probabilities and their mapping to colors. From green to red, it represents the suspicious score and from colorful to white the confidence score. For a developer, you need to know that colors express the failure cause probability (from red as high to green as low).
 
- ''Single Fault'' button::
+ ''Single Fault'' button:: If you can ensure that you debug only one failure at a time, then this button filters some failure cause probabilities and simplifies the debugging process. All methods that are not covered by all failing tests are hidden because it is necessary that for one root cause all failing tests have to overlap (''origination condition'' of single faults). 
 
- ''Highscore'' button::
+ ''Highscore'' button:: Lists all failure cause probabilities and their methods in descending order. 
 
- ''Developer Ranking'' button::
+ ''Developer Ranking'' button:: Recommends other developers that are able to help with this failure. 
 
 === Induction Flap ===