| 11 | | We enhance the standard browser with mainly five new features. |
| 12 | | First, we reuse the already collected [wiki:path:tutorial:tqf test coverage] data from [wiki:path:pathMap PathMap] and present it in a new pane on the right side. |
| 13 | | With a click on a corresponding test case, developers can start a symbolic debugger or our [wiki:path:pathFinder PathFinder]. |
| 14 | | Both tools stop their execution at the first call of the selected method and provide insights into its concrete run-time behavior. |
| 15 | | Second, based on the already collected test coverage, developers can also refine coverage data at statements on demand. |
| 16 | | For that, we re-execute all covering tests, analyze the currently selected method, and present the executed statements by underlining the corresponding source code. |
| 17 | | Third, with the help of our [wiki:path:tutorial:typeHarvesting type harvesting] approach, we have already gathered type information for instance variables, arguments, and return values from test cases. |
| 18 | | To support program comprehension during implementation tasks, we present this data with overlays that appear when developers mark a related variable. |
| 19 | | Fourth, we extend the browser with dynamic contracts from our [wiki:path:tutorial:tdfn test-driven fault navigation]. |
| 20 | | There are buttons for displaying the source code of invariants (inv), pre- and post-conditions (pre/post). |
| 21 | | Developers can also add manual assertions to this source code. |
| 22 | | Finally, we offer a button to open a [wiki:path:tutorial:modelbasedEditor model-based source code view] directly from the selected class or method snippet. |
| | 11 | We enhance the standard browser with mainly five new features: |
| | 12 | |
| | 13 | * '''Test coverage:''' We reuse the already collected [wiki:path:tutorial:tqf test coverage] data from [wiki:path:pathMap PathMap] and present it in a new pane. With a click on a corresponding test case, developers can start a symbolic debugger or our [wiki:path:pathFinder PathFinder]. Both tools stop their execution at the first call of the selected method and provide insights into its concrete run-time behavior. |
| | 14 | |
| | 15 | * '''Statement coverage refinement:''' Based on the already collected test coverage, developers can also refine coverage data at statements on demand. For that, we re-execute all covering tests, analyze the currently selected method, and present the executed statements by underlining the corresponding source code. |
| | 16 | |
| | 17 | * '''Type information:''' With the help of our [wiki:path:tutorial:typeHarvesting type harvesting] approach, we have already gathered type information for instance variables, arguments, and return values from test cases. To support program comprehension during implementation tasks, we present this data with overlays that appear when developers mark a related variable. |
| | 18 | |
| | 19 | * '''Contracts:''' We extend the browser with dynamic contracts from our [wiki:path:tutorial:tdfn test-driven fault navigation]. There are buttons for displaying the source code of invariants (inv), pre- and post-conditions (pre/post). Developers can also add manual assertions to this source code. |
| | 20 | |
| | 21 | * '''!PathView:''' We offer a button to open a [wiki:path:tutorial:modelbasedEditor model-based source code view] directly from the selected class or method snippet. |
