What's New > Version 2020.08.b

Extra Spring Controller method tests

Release date: Aug 17, 2020

Addition of extra tests for certain Spring Controller methods. A number of issues have also been resolved.

Full Release Notes


  • Cover creates more tests for Spring Controller methods that accept optional or primitive typed arguments. [Ref: TG-12144]

Resolved Issues

  • CLI: Resolved an issue where unnecessary telemetry-related warning messages may appear in console output. [Ref: TG-12555]

  • IntelliJ Plugin: Resolved an issue where stack traces were logged to IntelliJ IDEA’s event log. Such stack traces are now only visible in log files. [Ref: TG-12515]

  • IntelliJ Plugin: Resolved an issue where a Failed to combine generated test with test code message may be logged whilst attempting to create tests for a method whose existing tests have been modified. [Ref: TG-12508]

  • Resolved an issue where Cover may consume large amounts of memory whilst creating tests which utilize mocking. [Ref: TG-12500]

  • IntelliJ Plugin: Resolved an issue where, on macOS, / may be erroneously replaced with System.getProperty("user.dir"), resulting in the creation of failing tests. [Ref: TG-12475]

  • IntelliJ Plugin: Resolved an issue where, following a refactoring of classes in Intellij IDEA, old class files were used to create tests which would fail to compile. [Ref: TG-12417]

  • IntelliJ Plugin: Resolved an issue where selecting Write Tests, on a class that does not compile, provokes Could not insert a test to be logged, followed by an IllegalArgumentException. [Ref: TG-12410]

  • Resolved an issue where tests were not created for Spring methods which require a @MockBean of an interface type, such as beans created via @Bean factory methods. [Ref: TG-12138]

  • IntelliJ Plugin: Resolved an issue where selecting ‘Write tests’ across multiple modules, in quick succession, can cause the plugin to crash with a NullPointerException. [Ref: TG-12022]

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: Countly-related log messages may appear during execution. [Ref: TG-12565]

Dependencies for written tests

  • JUnit: 4.7-5.6