Changes between Version 37 and Version 38 of path:pathMap

Timestamp:

12/13/2013 04:26:20 PM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathMap

@@ -111 +111 @@
  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:: 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). 
+ ''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 test cases overlap (''origination condition'' of single faults). 
 
  ''Highscore'' button:: Lists all failure cause probabilities and their methods in descending order. 
 
- ''Developer Ranking'' button:: Recommends other developers that are able to help with this failure. 
+ ''Developer Ranking'' button:: Recommends experienced developers for helping with this failure. 
 
 === Induction Flap ===
@@ -125 +125 @@
 [[Image(inductionFlap.png)]]
 
- ''No Harvester'' drop down list (top)::
+ ''No Harvester'' drop down list (top):: Choose the inductive analysis mode. So far, we support the analysis of type information and value ranges. 
 
- Color legend::
+ Color legend:: Depending on the analysis, this legend shows the colors for the summarized results in our tree map. 
 
- ''Add Contracts'' button:: TODO REF TO PATHBROWSER! Results can be seen in PathBrowser...
+ ''Add Contracts'' button:: After the inductive analysis is done and results are available, this button allows developers to add derived likely invariants as assertions and contracts to the involved methods. This works completely automatic and can be seen afterwards in our [wiki:path:pathBrowser PathBrowser]. The contracts will be built with all available likely invariants and not only with the last analysis run.  
 
- ''Remove Contracts'' button::
+ ''Remove Contracts'' button:: Removes existing contracts from the source code. Also manually adapted contracts will be deleted.
 
 === Traceability Flap ===