IntelliJ plugin: disabling the sandboxing policy

By default, Cover runs with the Java sandbox turned on because we do not want to cause any undesired behavior on the system environment with such scenarios as: removing files on disk, initiating network traffic or making live database calls. Furthermore, these operations can also cause non-deterministic behavior. We attempt to mock out this I/O, but there are situations where we can’t and in these situations we may not produce a test.

Turning off the sandbox when you are running in a safe environment could allow Cover to get more coverage for this code, thus allowing you to look at refining mocking controls and other behavior. Please use this option with caution! There is now a new option in the IntelliJ plugin to disable sandboxing. By default it is enabled, as is shown below:

CLI: additional dependency recommendation

Developer Edition trial available

We are delighted to now offer a 14-day trial version of our Developer Edition, which includes the Diffblue Cover CLI, as part of our new licensing option. We're really excited that you can now "try before you buy"! To download your trial of Diffblue Cover Developer Edition, please click here. Full information on all our options is also available here.

How do I automatically maintain all of these tests?

Use Diffblue Cover on any CI platform to automatically update your unit tests and catch regressions for every commit - watch this video to learn more.


  • CLI: Cover now recommends a specific dependency when the specified test framework is not on the classpath. [Ref: TG-17656]

  • CLI: Cover now skips build system detection when there is no build configuration file. [Ref: TG-17655]

  • IntelliJ Plugin: Cover's sandbox environment is now configurable via the plugin settings. [Ref: TG-17586]

  • IntelliJ Plugin: Cover now avoids adding duplicate simple assertions to existing tests when ‘Write Tests’ is executed on the same method/class/package multiple times. [Ref: TG-17541]

  • Cover test creation performance has been improved, reducing time required to write tests. [Ref: TG-17491]

Resolved Issues

  • IntelliJ Plugin: Resolved an issue where tests using assertThrows or assertDoesNotThrow (and JUnit 4 equivalents) were not de-duplicated. [Ref: TG-17607]

  • IntelliJ Plugin: Resolved an issue which, in some circumstances, could cause Cover to hang whilst attempting to write tests for an invalid module. [Ref: TG-17582]

  • IntelliJ Plugin: Resolved some cosmetic inconsistencies in the plugin settings. [Ref: TG-17431]

Known Issues

  • CLI: The command dcover clean --failing does not work on Gradle projects. This command is now deprecated and dcover validate should be used instead. [Ref: TG-11707]

  • For multi-module projects, --coverage-reports needs to be run in the sub-modules, not from root module with --working-directory. [Ref: TG-16876]

Last updated