#1125 Test aggregation plugin: update dependencies and 'test-all' launch configuration + check for consistency
- Best to review per commit.
- No end-user visible changes.
- Changes:
- The test aggregation project now has all test projects (except itself) as a dependency. It got out of sync, but this update brings it back in sync. Most dependencies are in the manifest, but ones that can't be (Maven-only projects) are in the POM.
- The test aggregation projects'
test-all
launch configuration is a group launch configuration that launches a launch configuration for each project with tests, to be able to run all tests. It also got out of sync, but is now back in sync. It includes a launch configuration for each project with tests, including itself. - To prevent getting out of sync again and us not noticing, there are now two unit tests to check that the dependencies and
test-all
launch config are in sync. This also makes sure that theproblemreporter.run
project remains last in the build order. - Removed
test-cif-cif2mcrl2.launch
as the project doesn't have tests anymore. - I removed the Maven nature on two projects, to make sure it all works both in the development environment and in the Maven/Tycho build.
- To ensure that the test aggregation project's own tests are considered when aggregation test results and determine code coverage, I had to change the phases in which some of the Maven plugins run.
- I compared the output of build nr 1 of the branch (before any changes) against build nr 2 (with all changes). It was as expected.
Closes #1125 (closed)