| 33 | | To localize failure causes in behavior, developers start exploration either directly at a failing test case or out of covered suspicious methods as provided by PathMap. |
| 34 | | Subsequently, PathFinder opens at the chosen method as shown in Figure 6.4 and allows for following the infection chain back to the failure cause. |
| | 33 | * First, you need a proper Path project that is selected as current. For more information see [wiki:path:pathProject PathProject]. |
| | 34 | * To start !PathFinder choose the tool either in the world docking bar at the top (Apps -> !PathFinder) or in the world menu (open... -> !PathFinder). |
| | 35 | * After that, you will see a tool as in the screenshot above with a large white space in the middle. |
| | 36 | * In order to get the execution history of a specific test case, please click on the rectangle in the upper left corner and choose the corresponding test case from the list. |
| | 37 | * Afterwards, the executed call tree is presented in the former white area below and developers can start exploring its execution history. |
| | 38 | |
| | 39 | '''Note:''' Developers can start exploration either directly at a test case or out of covered methods as provided by [wiki:path:pathMap PathMap]. |
| | 40 | Subsequently, !PathFinder opens at the chosen method instead of the test case's beginning. |
