What's New > Version 2020.09.01
Enhanced mocking and version detection
Release date: Sep 14, 2020
Diffblue Cover now has enhanced mocking and version detection. Some performance improvements have also been included.
Full Release Notes
Enhancements
-
CLI: Cover performance improvements. [Ref: TG-12593]
-
Cover now allows the use of mocking, in Spring projects, to be limited via the
--spring-integration-tests
CLI option orEnable Spring integration tests
checkbox via the IntelliJ Plugin settings. [Ref: TG-12176] -
CLI: Cover now reports detected versions of Java, JUnit and Mockito to the console during test creation. [Ref: TG-11154]
Resolved Issues
-
IntelliJ Plugin: Resolved an issue where
Created new test
events may not be logged to the IntelliJ event log. [Ref: TG-12693] -
CLI: Improved guidance around actions to be taken after adding a new module to a Maven project. [Ref: TG-12600]
-
CLI: Resolved an issue where tests were not generated for methods which create temporary files. Tests will now be generated, as long as they also delete those files. [Ref: TG-12488]
Known Issues
-
Wrong reason for not creating essential tests for methods in classes without accessible constructors. [Ref: TG-10794]
-
CLI: Windows: creating
config.json
by outputting--example-config
as file causes exceptions. [Ref: TG-11198] -
CLI: All tests may be discarded in test verification when using
--config
. [Ref: TG-11475] -
CLI:
dcover clean --working-directory
throws an error if--test-output-dir
is not provided. [Ref: TG-11665] -
CLI: dcover fails to generate tests, reporting
java.lang.OutOfMemoryError
, when analysing projects which spawn a quantity of threads in excess of the operating system’s process thread limit. [Ref: TG-11680] -
CLI:
dcover clean --failing
fails when used with a Gradle project. [Ref: TG-11707] -
Tests are not generated for methods of Spring controllers that contain an autowired field. [Ref: TG-11835]
-
CLI: Test verification may fail on a Gradle project due to an incompatibility between Gradle and Cover. If you encounter this issue, run with
--skip-test-verification
. [Ref: TG-12045] -
CLI: Test verification does not work with JUnit versions 5.0 to 5.3. [Ref: TG-12353]
Dependencies for written tests
- JUnit: 4.7-5.6