projects / deliverable / tracecompass.git / blame
| Commit | Line | Data |
|---|---|---|
| be3347d9 | 1 | # tracecompass-rcptt-test |
| 87dd36aa | 2 | |
| be3347d9 JR |
3 | Blackbox UI test using RCPTT for Trace Compass |
| 4 | ||
| 5 | ## How to run ? | |
| 6 | ||
| 7 | You can run this project either via maven or via the RCP Testing Tool. | |
| 8 | ||
| 9 | ### Local maven run | |
| 10 | ||
| 87dd36aa | 11 | `mvn clean install` |
| be3347d9 | 12 | |
| 87dd36aa | 13 | Results will be located under `./target/results`. |
| be3347d9 | 14 | |
| 87dd36aa | 15 | By default maven will use the RCP built in `../rcp/org.eclipse.tracecompass.rcp.product`. |
| be3347d9 | 16 | Therefore, if you only want to execute the tests in this folder and not the rest of the build, |
| 87dd36aa | 17 | you need to make sure that the product has been built first (`mvn clean install -Dmaven.test.skip=true` in the git repository root folder). |
| be3347d9 | 18 | |
| 87dd36aa | 19 | Test traces are being made available in a path defined as the `dataPath` system property. The test traces are being downloaded as part of the maven build and extracted in `./target/dependency/tracecompass-test-traces-ctf-jar/`. |
| be3347d9 JR |
20 | |
| 21 | ### Via RCPTT | |
| 22 | ||
| 23 | In order to have the RCP and test traces, it is better to run with Maven first. | |
| 24 | Once this is done, the project (this directory) can be imported in RCPTT. | |
| 25 | ||
| 87dd36aa | 26 | To run the tests, open `test_suite/open_trace_suite` then click Execute at the top-right corner |
| be3347d9 JR |
27 | |
| 28 | A predefined launch is provided to ease with launching the tests. | |
| 29 | This launch sets up the AUT path and dataPath (test traces). | |
| 30 | ||
| 31 | If you are not using the default paths make sure to pass the correct arguments to | |
| 32 | the AUT in the run configurations. | |
| 33 | ||
| 34 |  |