Setting withHistory disables historyInputFile and historyOutputFile
See original GitHub issueIt took me a while to figure this out and I had to go through your code to find it. In MojoToReportOptionsConverter the following code uses the default temp location when withHistory is set to true. In that case the historyInputFile and historyOutputFile are ignored. To me it would be more logical that when withHistory is set a check is done to see if the locations are set and use those instead of the tmp location. If you want I can make a pull request but I’d have to get set up first.
private void determineHistory(final ReportOptions data) {
if (this.mojo.useHistory()) {
useHistoryFileInTempDir(data);
} else {
data.setHistoryInputLocation(this.mojo.getHistoryInputFile());
data.setHistoryOutputLocation(this.mojo.getHistoryOutputFile());
}
}
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Quickstart for maven users - PIT Mutation Testing
withHistory. Sets the history input and output files to point a project specific file within the temp directory. This is a convenient way...
Read more >PITEST incremental analysis cannot find local hash file
There looks to be a bug which stops things working if both are set. This needs to be fixed, but setting both doesn't...
Read more >Real world mutation testing - Cornell CS
To speed-up repeated analysis of the same codebase set the withHistory parameter to ... If the feature FLOGCALL is disabled, this parameter is...
Read more >Mutation Testing: Automate the Search for Imperfect Tests
Unless the test is run with the -ea flag set on the command line, the test ... The withHistory flag tells pitest to...
Read more >Mutation Testing - Who will test the tests themselves?
The specified configuration parameters are as follows: historyInputFile/historyOutputFile - Together these values activate the incremental ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree with peter-janssen. It is essential that these are checked in the correct order, and both have effects as described in the FAQ. I was struggling to set up the suite because I thought that they have to be used together in order to use a different path and use history. Also, the log doesn’t display “Using history file …” when only using the location parameters, which suggests that there is no history file being used. TL;DR: At least document in the FAQ how these 3 properties actually work.
Agreeing with @peter-janssen as well, it confused me too 😃