Release notes for release 2020.03.c

Release date: March 30th, 2020

Release highlight

  • IntelliJ Plugin: The status of test creation for each method is now displayed clearly in the progress bar and event log. [Ref: TG-11445]

  • CLI: Besides the classpath, we now also detect the testing framework, version, compliance level and the test verification command automatically from the Maven configuration. [Ref: TG-10890]


  • CLI: The compatability of the the JUnit version is checked earlier now so as to give feedback to the user quickly. [Ref: TG-11429]

  • CLI: By default, tests that check whether exceptions have been thrown are not created anymore. To create them add the flag --exception-tests. [Ref: TG-11399]

  • CLI: The choice of input values for strings (in particular matching regexes) and use of setters has been improved. [Ref: TG-11215, TG-11448, TG-11214]

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: Tests created for Spring projects may be incompatible with existing tests. [Ref: TG-11459]

  • 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: on projects that specify precise maven-help-plugin CLI may fail to detect that the project is multi-module. [Ref: TG-11481]

  • CLI: Writing tests for code that deletes files may cause Cover to abort with an unexpected error. [Ref: TG-11540]

  • CLI: Sometimes Cover non-deterministically hangs. [Ref: TG-11547]

Dependencies for written tests

  • JUnit: 4.7-5.5

results matching ""

    No results matching ""