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:

  1. 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
  2. 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 the dcover command is run. These files include:
    1. Logs being created in ./.diffblue/log
    2. advisories.txt, report.json and JaCoCo coverage reports created in ./.diffblue/reports
    3. Cover Optimize: selected-tests.json created in ./.diffblue
    4. Cover Refactor: refactorings.yml created in ./.diffblue
  3. 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:
    1. The dcover command writing tests for the module in the directory <module path>
    2. Logs being created in <module path>/.diffblue/logs
    3. advisories.txt, report.json and JaCoCo coverage reports created in <module path>/.diffblue/reports
    4. Cover Optimize: selected-tests.json created in <module path>/.diffblue
    5. Cover Refactor: refactorings.yml created in <module path>/.diffblue

Should you have any questions about this  please do contact our support team via https://go.diffblue.com or email [email protected]