Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combine results of test suites #1

Open
Cael35 opened this issue Dec 9, 2017 · 3 comments
Open

Combine results of test suites #1

Cael35 opened this issue Dec 9, 2017 · 3 comments
Assignees

Comments

@Cael35
Copy link

Cael35 commented Dec 9, 2017

Results focus on a test suite.
It would be useful to combined test results focus on a package, and combining results of all test suites which use the package.

@Cael35
Copy link
Author

Cael35 commented Apr 12, 2018

We can use the new report-aggregate mojo available in release 1.3.2.
Documentation is available on pitest.org:
http://pitest.org/aggregating_tests_across_modules

@gibello
Copy link
Contributor

gibello commented Sep 27, 2019

If I specify a <reportsDirectory> in the plugin config, this is not any more a functionality... but a bug : multiple modules can be output in the same directory (if they start in the same minute, they correspond to the same timestamp, used for the directory name), and the index.html is overwritten (the last module wins !).

@oscarlvp
Copy link
Member

oscarlvp commented Oct 8, 2019

There is a workaround for the specific problem @gibello is having.
In the root pom.xml file you can configure the <reportsDirectory> as follows:

<configuration>
    <reportsDirectory>
         /path/to/report/${artifactId}
     </reportsDirectory>
     <timestampedReports>false</timestampedReports>
</configuration>

in this way, all report will be generated in /path/to/report/ and then, inside, the report of each module will be stored in a folder named after the module and therefore they will be not overwritten.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants