What's New > Version 2020.08.c
IntelliJ IDEA 2020.2 support
Release date: Aug 30, 2020
Diffblue Cover now supports IntelliJ IDEA 2020.2.
Full Release Notes
Enhancements
- IntelliJ Plugin: Cover now supports IntelliJ IDEA Community Edition 2020.2 and IntelliJ IDEA Ultimate 2020.2. [Ref: TG-12607]
Resolved Issues
-
CLI: Resolved an issue where Countly-related log messages may appear during execution. [Ref: TG-12565]
-
IntelliJ Plugin: Resolved an issue where Cover may not detect appropriate JUnit version from Gradle projects. [Ref: TG-12556]
-
IntelliJ Plugin: Resolved an issue where one or more
Checking environment and preparing to write tests
background tasks may persist beyond test creation. [Ref: TG-12539] -
IntelliJ Plugin: Resolved an issue where selecting ‘Write Tests’ on a class, or method, within a module which contains spaces in the module name, results in a
IllegalArgumentException
. [Ref: TG-12538] -
IntelliJ Plugin: Resolved an issue where running failing tests, with Cover’s
Compute Changes in Coverage
option enabled, may result in aNullPointerException
. [Ref: TG-12530] -
CLI: Resolved an issue where the expanded classpath output may be
[truncated]
. This output is no longer truncated, in the console output or logfile, when –verbose is specified. [Ref: TG-12519] -
IntelliJ Plugin: Resolved an issue where a
NullPointerException
may be thrown when selecting ‘Write Tests’ on a method which has not been indexed by Cover. [Ref: TG-12518] -
CLI: A JDK available in JAVA_HOME (if any) will now be used during test verification for Gradle projects. [Ref: TG-12397]
-
IntelliJ Plugin: Removed spurious error about missing Spring dependencies. [Ref: TG-12009]
-
CLI: Resolved an issue where Cover could not write tests for projects with JUnit dependencies packaged into fat jars. [Ref: TG-11390]
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