Release number:         2019.11.a

Release date:                November 4, 2019

Release Highlight

  • The plugin now uses the IntelliJ build configuration which makes it unnecessary to specify the location of the Maven executable and enables Gradle builds.

Additional Enhancements

Cover usability:

  • The plugin optionally provides Diffblue with basic information for product improvement (IntelliJ version, Diffblue Cover version, operating system, RAM, CPU).
  • Windows 10 Enterprise and Home are now supported.
  • JaCoCo and IntelliJ’s internal coverage measurement are supported now and can be selected in the preferences.

Significant bug fixes

IntelliJ Plugin: 

  • The IntelliJ plugins configuration settings are lost after IDE restart (TG-9965) bug is now fixed.
  • The pom file of Maven projects need not be configured to produce a fat jar anymore (TG-9345).

Known issues

Basic-test mode doesn’t currently work for differential analyses or produce any coverage information.

IntelliJ: IntelliJ’s internal coverage measurement requires a JUnit run configuration named `cover-tests-run` to work correctly. [Ref: TG-10247]

IntelliJ: Currently only supports single-module Maven projects. [Ref: TG-9749]

IntelliJ: Tests are automatically integrated into the code base in src/test/java relative to the project’s root. Test classes are placed in the same package as the class used to create the tests and the classes are named by appending Test to the name of the generating class.  [Ref: TG-9346]

IntelliJ: Advanced configuration of the analysis is via a diffblue.json file placed in the project directory (rather than using the yml file format).

IntelliJ: The completion time is an estimate based on the projected time for the analysis.  [Ref: TG-9347]

IntelliJ: Preferences are set globally and not on a per-project basis.  [Ref: TG-9348]

Web-UI: When a build and /or differential analyses are started from the plugins API, the results returned appear to be correct.  However, when inspected via the Web-UI, the analyses show as failed with the error message `test verification process failed. [Ref: TG-9809]

Web-UI: If an analysis doesn’t return any tests ranked 3 stars or higher, the help function on the Tests tab doesn’t work. [Ref: TG-9808]

Dependencies for written tests

deeptest-utils

1.9.0

Junit

4.8

Powermock

1.6.5

Mockito

1.10.19

Detailed Feature support overview for Cover

2019.10.b

2019.11.a

2019.11.b

2019.12.a

Environment

Operating Systems

Windows 10 Professional

yes

yes

yes

yes

Windows 10 Home

-

-

yes

yes

Ubuntu 18.04

-

-

yes

yes

Mac OSX 10.14

-

-

yes

yes

IntelliJ Versions

IntelliJ Community 2019.2

yes

yes

yes

yes

IntelliJ Ultimate 2019.2

-

yes

yes

yes

Java Input

JDK 8

yes

yes

yes

yes

Uses IDE-supplied build configuration

-

yes

yes

yes

Rebuilds project automatically

yes

yes

yes

yes

Classpath to .class and .jar files

-

yes

yes

yes

Fat jar

yes

yes

yes

yes

Supports non-Spring code in Spring projects

-

-

yes

yes

Java Output

JDK 8

yes

yes

yes

yes

JUnit 4.8

yes

yes

yes

yes

Tests automatically merged into source tree

yes

yes

yes

yes

Tests are merged in order of declaration in the implementation class

yes

yes

yes

yes

Test Naming

Test classes named by user-defined template (incl. class name)

-

-

yes

yes

Test methods named by user-defined template (incl. method name)

-

-

yes

yes

Test Code Style

Inline immediate values

yes

yes

yes

yes

Inline dot-expressions that are used only once

yes

yes

yes

yes

Allow for inlining "arrange" into "act" or "assert"

yes

yes

yes

yes

Allow for inlining "act" into "assert"

-

-

yes

yes

Inline constructor calls

-

-

yes

yes

Coverage Measurement Features

Coverage Increment Indicators

Uses IntelliJ coverage measurement

yes

yes

yes

yes

Uses JaCoCo

-

yes

yes-

yes

Can be turned on/off in configuration, default on

-

yes

yes

yes

Indicators can be reset by user

-

yes

yes

yes

Do not generate tests for covered code

yes

yes

yes

yes

Assertion Suggestions Feature

By context menu / key shortcut within test method

-

-

yes

yes

Write Tests Feature

Test Generation Engine

Locally available

-

-

yes

yes

Can configure remote engine

yes

yes

yes

-

Can select remote engine if configured

yes

yes

yes

-

Boilerplate Mode

Is available

-

-

yes

yes

Runs as fallback after basic-test method

-

-

yes

yes

Can be turned on/off in configuration, on by default

-

-

yes

yes

Basic-Test Mode

Is available

-

-

yes

yes

Runs as fallback after deep-test mode

-

-

yes

yes

Can be turned on/off in configuration, on by default

-

-

yes

yes

Deep-Test Mode

Is available

yes

yes

yes

-

Can be turned on/off in configuration, on by default

-

-

yes

-

Test Generation Scope

Per method

yes

yes

yes

yes

Per class

yes

yes

yes

yes

Per package

yes

yes

yes

yes

Per module

yes

yes

yes

yes

Per project

-

-

-

-

Multiple projects

-

-

-

-

Support and Product improvement

Online documentation

yes

yes

yes

yes

Online release notes

yes

yes

yes

yes

Online data sheet

-

-

-

-

Setup wizard to set remote engine configuration

yes

yes

yes

yes

Welcome area with links to documentation

yes

yes

yes

yes

"Diffblue Cover was installed" notification

yes

yes

yes

yes

Environment analytics data, on by default

-

yes

yes

yes

Behavioural analytics data, on by default

-

-

yes

yes

Analytics can be turned off in configuration

-

yes

yes

yes

Automatic bug reporting

-

-

yes

yes

Automatic bug reporting can be turned off in configuration

-

-

yes

yes

Support request form

-

-

yes

yes

Notification about availability of new version

-

-

yes

yes

Page   © Diffblue Ltd. 2019 All rights reserved.