What's New > Version 2020.05.b

Support for JUnit 5.6

Release date: May 26, 2020

Cover now supports projects which have JUnit 5.6.x as a dependency. It also now produces tests for multiple paths in Spring Controller methods.

Full Release Notes


  • IntelliJ Plugin: Hints are now provided, in IntelliJ’s event log, explaining why Cover considered a method not testable. [Ref: TG-11831]

  • CLI: Progress bars have been updated, removing Unicode characters, to improve rendering across widely used terminals. [Ref: TG-11781]

  • CLI: Cover no longer attempts to create tests for main() methods as there is nothing to assert. [Ref: TG-11780]

  • Cover now supports projects which have JUnit 5.6.x as a dependency. [Ref: TG-11524]

  • Cover is now able to produce tests for multiple paths in Spring Controller methods. [Ref: TG-11408]

Resolved Issues

  • IntelliJ Plugin: The ‘Enable Spring Support’ setting is redundant as Cover is now able to autodetect the presence of Spring in projects. It has been removed now. [Ref: TG-11843]

  • IntelliJ Plugin: Selecting ‘Suggest Assertions’ on an indented, but otherwise empty, line can result in an un-indented assertion being inserted. [Ref: TG-11822]

  • CLI: checkstyle and spring-javaformat Maven plugins can cause test verification to fail. [Ref: TG-11784]

  • CLI: Dcover outputs many We detected Spring on the classpath, but were missing critical classes to load our own context messages whilst analyzing Spring projects. [Ref: TG-11672]

  • CLI: During project analysis, some console output may be suppressed intermittently. Complete output remains available in the logfile. [Ref: TG-11608]

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: Spring projects that use logback may turn off the console and log file output. [Ref: 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]

  • 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]

  • IntelliJ Plugin: Selecting ‘write tests’ on multiple classes, in quick succession, results in tests not being generated for some classes. [Ref: TG-11713]

  • IntelliJ Plugin: Not clicking “Suggest Assertions” for a long period (~1 hour) leads to user getting the message “Cannot generate assertions” for every subsequent assertion suggestion attempt. [Ref: TG-11817]

  • Tests are not generated for methods of Spring controllers that contain an autowired field. [Ref: TG-11835]

Dependencies for written tests

  • JUnit: 4.7-5.6