Release notes for release 2019.12.b
Release date: December 16, 2019
When using our CLI, you now have the option to only create tests for uncovered methods.
In our IntelliJ plugin we will tell you if Diffblue Cover can't create a test for a certain method along with the reason why.
We have made our CLI more intuitive.
If a classpath isn't provided, the CLI will attempt to detect that the project uses Maven and infer the classpath from the Maven configuration.
IntelliJ: Preferences are set globally and not on a per-project basis. [Ref: TG-9348]
IntelliJ: On macOS, tests are not created when launching the plugin via the Dock or the Applications folder. The workaround is to launch the plugin via the command line. [Ref: TG-10544]
IntelliJ: 'Suggest assertions' sometimes errors with
AssertionSuggestionException: Runner timeoutcausing the feature to become unavailable. Restarting IntelliJ usually makes it available again. [Ref: TG-10798]
Intellij: If writing essential test on an instance method of a class without accessible constructor fails then a wrong warning is shown stating that the method itself is unaccessible. [Ref: TG-10794]
CLI: If the analyzed module has a very long classpath then on Windows the CLI aborts with a message
Command line too long. A workaround is to pass a fat JAR file instead of the classpath enumerating the dependencies. [Ref: TG-10787]
CLI: If the analyzed module has a logback.xml file then logback warnings are displayed while running the CLI. [Ref: TG-10793]
CLI: Sometimes output from threads in the analyzed module is displayed while running the CLI. [Ref: TG-10792]
CLI: No tests are written for classes in the default package. [Ref: TG-10786]
Dependencies for written tests
- JUnit: 4.8