Diffblue Logo
Go to diffblue.com

Get unit tests for your Java code automatically with our free IntelliJ plugin. Download now

What's New > Version 2020.09.02

Improved stability and reporting

Release date: Sep 28, 2020

Improved stability of test creation for projects which contain multi-threaded code, and improved reporting on tests which have been discarded during test verification.

Full Release Notes

Enhancements

  • Improved stability of test creation for projects which contain multi-threaded code. [Ref: TG-12762]

  • CLI: Improved statistics and reporting for tests which have been discarded during test verification. Per-method reasons for discarded tests are logged to the console when using the --verbose option. [Ref: TG-11630]

Resolved Issues

  • IntelliJ Plugin: Resolved an issue where, in environments which prefer IPv6 over IPv4, Failed to establish a connection to the test generation service. may be logged to the console and no tests are created. [Ref: TG-12749]

  • CLI: Resolved an issue where appropriate guidance is not logged to the console when the required javax.cache dependency is missing. [Ref: TG-12746]

  • IntelliJ Plugin: Resolved an issue where test creation logging was not recorded in cover-plugin.log and cover-plugin-server.log. [Ref: TG-12606]

  • CLI: Resolved an issue where Cover may fail to create tests, reporting R014: Could not start test generator because the JDK could not be found when using a minimal Java 11 package. [Ref: TG-12545]

  • IntelliJ Plugin: Resolved an issue where tests may be inserted into the wrong module, if more than one module contain the same package and class names. [Ref: TG-12450]

  • CLI: Resolved an issue where tests may be discarded with V002 Execution error whilst using JUnit versions 5.0 to 5.5. [Ref: TG-12353]

  • CLI: Resolved an issue where, for projects which have a dependency on javax.annotation, tests created by Cover may incorrectly fail verification. [Ref: TG-12208]

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]

Dependencies for written tests

  • JUnit: 4.7-5.6