| | 37 | * First, you need a proper Path project that is selected as current and already [wiki:path:tutorial:typeHarvesting harvested type information]. For more information see [wiki:path:pathProject PathProject]. '''Note:''' It also works without a project and type information but then it is more manual work than necessary. |
| | 38 | * To start !PathView choose the tool either in the world docking bar at the top (Apps -> !PathView) or in the world menu (open... -> !PathView). |
| | 39 | * After that, you will see a tool as in the screenshot above with a large white space in the middle. |
| | 40 | * In order to create your first diagram, open a standard source code browser, select a corresponding class within your project, and drag'n'drop it within the white area. Answer the question for automatically creating connection with yes and our analysis techniques try to create associations and inheritance relationships of this class automatically. |
| | 41 | * Now you can refine your diagram step by step as described below. |
| 42 | | * First, you need a proper Path project that is selected as current. For more information see [wiki:path:pathProject PathProject]. |
| 43 | | * To start !PathFinder choose the tool either in the world docking bar at the top (Apps -> !PathFinder) or in the world menu (open... -> !PathFinder). |
| 44 | | * After that, you will see a tool as in the screenshot above with a large white space in the middle. |
| 45 | | * 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. |
| 46 | | * Afterwards, the executed call tree is presented in the former white area below and developers can start exploring its execution history. |
