What's New > Version 2020.04.a
Gradle configuration detection and Spring Repository Beans mocked
Release date: Apr 14, 2020
Gradle configuration is now automatically detected, and Spring Repository Beans are mocked using @MockBean and Mockito. Tests are now created that require calling setter methods and require more complex constructors, increasing the number of branches tested.
Full Release Notes
Enhancements
-
Gradle configuration is now automatically detected. [Ref: TG-10902]
-
Spring Repository Beans are mocked using
@MockBean
and Mockito. [Ref: TG-11192] -
Tests are now created that require calling setter methods, increasing the number of branches tested. [Ref: TG-11214, TG-11526]
-
Tests are now created that require more complex constructors, increasing the number of branches tested. [Ref: TG-11225]
-
Tests now try several implementation classes, increasing test coverage. [Ref: TG-11226]
-
Tests which assert on local environment configuration are no longer created. [Ref: TG-11544]
-
CLI: Summary information on reasons for not creating tests is now provided by default. [Ref: TG-11520]
-
CLI: Hints for resolving issues which prevent tests from being created tests are now displayed. [Ref: TG-11529]
-
IntelliJ Plugin: Links to generated tests are now provided in the event log. [Ref: TG-11548]
Known issues
-
Wrong reason for not creating essential tests for methods in classes without accessible constructors. [Ref: TG-10794]
-
IntelliJ Plugin: cancelling the indexing job causes exception. [Ref: TG-11074]
-
IntelliJ Plugin: Test combining can incorrectly merge tests, leading to non-compiling tests. [Ref: TG-11175]
-
CLI: Windows: creating
config.json
by outputting--example-config
as file causes exceptions. [Ref: TG-11198] -
IntelliJ Plugin: Spring test generation is very slow. [Ref: TG-11380]
-
IntelliJ Plugin: Spring tests are sometimes merged incorrectly. [Ref: TG-11381]
-
CLI: Spring projects that use logback may interfere with the console and log file output. [TG-11440]
-
CLI: Analyzing a project that opens lots of files may crash dcover. [Ref: TG-11455]
-
CLI:
clean --failing
may not remove all failing tests when tests are inter-dependent. [Ref: TG-11472] -
CLI: All tests may be discarded in test verification when using
--config
. [Ref: TG-11475] -
IntelliJ Plugin: Suggested assertion inserted above a comment line even though the cursor was below it. [Ref: TG-11478]
-
CLI: Sometimes Cover non-deterministically hangs. [Ref: TG-11547]
-
Gradle classpath detection does not work with Gradlew in Gradle version 4.8.1. [Ref: TG-11651]
-
Gradle classpath detection –working-directory does not work for Windows. [Ref: TG-11652]
-
CLI: Misleading error message shown when Maven project dependencies are empty. [Ref: TG-11660]
-
CLI:
dcover clean --working-directory
throws an error if--test-output-dir
is not provided. [Ref: TG-11665]
Dependencies for written tests
- JUnit: 4.7-5.5