Knowledge Base > Troubleshooting > Update to working-directory (Release 2022.08.05)
Update to --working-directory
(Release 2022.08.05)
As part of our continual improvement of Cover, we are looking to make deployment easier. We have identified inconsistencies between the two command line options --target-directory
and --working-directory
that are currently used for setting folder paths. We are simplifying this so we now only have one option for specifying folder paths --working-directory
, which has also resulted in changes to its behavior. In the 2022.08.05 release we are:
- Removing the
--target-directory
option previously used to set the directory for storing Cover’s working files and logs. If you are currently using the--target-directory
option then your existing configuration will no longer work. - By default with neither option specified, the dcover command will write tests for the module in the working directory where the dcover command is run; furthermore all working files will be placed in the
.diffblue
folder in the same working directory from where thedcover
command is run. These files include:- Logs being created in
./.diffblue/log
advisories.txt
,report.json
and JaCoCo coverage reports created in./.diffblue/reports
- Cover Optimize:
selected-tests.json
created in./.diffblue
- Cover Refactor:
refactorings.yml
created in./.diffblue
- Logs being created in
- To override this default location, use the
-–working-directory <module path>
option which has also been updated as it was previously inconsistent; this will result in:- The
dcover
command writing tests for the module in the directory<module path>
- Logs being created in
<module path>/.diffblue/logs
advisories.txt
,report.json
and JaCoCo coverage reports created in<module path>/.diffblue/reports
- Cover Optimize:
selected-tests.json
created in<module path>/.diffblue
- Cover Refactor:
refactorings.yml
created in<module path>/.diffblue
- The
Should you have any questions about this please do contact our support team via https://go.diffblue.com or email [email protected]