E - Environment Codes
Introduction
These output codes are associated with system checks performed on your development environment by Diffblue Cover. This ensures your environment is configured correctly and that Diffblue Cover is compatible with it.
E001 - Failed to insert a test
Diffblue Cover failed to write a test in the test Java file. Please enable read and write permissions on the file.
E002 - Failed to overwrite the created test Java file
Failed to overwrite the created test Java file. Please enable read and write permissions on the file and its parent folder.
E003 - Failed to read existing test Java file
Failed to read the existing test Java file. Please enable read permissions on this file and its parent folder.
E004 - No methods found to test
Diffblue Cover was unable to find any methods that can be tested in your selection. Ensure that your selection includes some Java code that contains methods that are not private.
If using the
--patch-only
option, ensure that the patch file was created correctly and that its encoding is UTF-8.
E005 - Parent module without classes
You must run
dcover
on the individual submodules. Run dcover with the option
--working-directory path/to/submodule
or change into the submodule directory and run
dcover
from there.
E006 - JUnit Jupiter Launcher not found
Diffblue Cover cannot verify the generated tests because the JUnit Jupiter Launcher was not found. We have detected that you have JUnit Jupiter on your classpath but were not able run a dummy test. Because of this, Diffblue Cover has disabled test verification.
Please ensure that your build system is configured to run JUnit Jupiter tests (for Maven projects, ensure the Surefire plugin is configured to run JUnit Jupiter tests; for Gradle projects, ensure that
useJUnitPlatform()
is in the
test
configuration.
You can also use
--testing-framework=junit-4
to force Diffblue Cover to write JUnit4 tests.
E007 - Missing classes detected
Diffblue Cover could not execute a Dummy Test in your project. A number of classes were detected as missing. Because of this Diffblue Cover will not be able to verify tests. Please resolve these missing classes to enable test verification.
E008 - Missing a critical JUnit Jupiter class
Diffblue Cover was not able to run a dummy test in your environment because the
ClassNamePatternFilterUtils
class was missing. This can occur when you have a mismatch in versions of the junit-platform-launcher and junit-platform-commons. Please ensure that these versions are consistent. If you don't have a junit-platform-launcher specified, please add an appropriate version to your project. Because of this Diffblue Cover will not be able to verify tests.
E009 - Unexpected launcher detection output
While trying to detect the path to the JUnit Jupiter Launcher, we detected multiple lines of output where we expected only a single line. Because of this Diffblue Cover will not be able to verify tests.
E010 - Invalid patch depth
The --patch-depth parameter controls the number of hops from the classes in the patch dcover will consider when generating tests. A value of 0 will create tests for just the classes in the patch, while a value of 1 will create tests for any class that uses those in the patch (as well as the ones mentioned in the patch), and so on.
Care must be taken as there are occasions where the impact of the changes in the patch may not be detected and you may end up with test failures because the impact of the patch hasn't propagated to the necessary extent.
E011 - Failed to run a simple example test
Problems in the local build system have been detected that will prevent Diffblue Cover from verifying and validating the created tests.
E012 - Error when using build system
An error occurred when using the build system. Check the user log file in
.diffblue/log
which contains the entire build system log to find the build system error message.
E013 - Compatible launcher not found
Diffblue Cover was unable to find a JUnit Jupiter Launcher compatible with your configured JUnit Jupiter Engine and therefore will not be able to verify tests. Please upgrade your build configuration to use a compatible JUnit Jupiter Engine versions.
E014 - No build system found
Neither Gradle nor Maven build systems were detected. Use the
--classpath
option or
CLASSPATH
environment variable to specify a classpath manually.
E015 - Specified build system not available
The specified build system is not available. Make sure a build configuration file for the specified build system is available in the project, or enable auto-detection of the build system by removing the
--gradle
or
--maven
options you might be using.
E017 - Trace loading error
Failed to load execution trace. Please review the cause message to diagnose the underlying issue.
E018 - Working directory does not exist
The specified working directory does not exist. Make sure you have specified an existing directory when using the
--working-directory
option.
E019 - Failed to create .diffblue directory
Diffblue Cover failed to create its
.diffblue
directory in the working directory. Make sure Diffblue Cover has the correct permissions to create a directory.
E021 - Multiple 'settings.gradle' files
There are multiple
settings.gradle
files in your project, which may cause your project configuration to be invalid. Consolidate the content of your
settings.gradle
files into a single file at the root of your project, and remove all other
settings.gradle
files.
E022 - JUnit Jupiter Launcher location
Diffblue Cover was not able to discover the path to the JUnit Jupiter Launcher. Because of this Diffblue Cover will not be able to verify tests.
E023 - A file could not be deleted
The given file could not be deleted. If deletion is necessary, please do this manually.
E024 - Multiple files could not be deleted
The given files could not be deleted. If deletion is necessary, please do this manually.
E025 - Unable to download the launcher
Diffblue Cover uses the JUnit Jupiter Launcher to run verify tests. While attempting to download the launcher we encountered an error. Because of this, Diffblue Cover has disabled test verification.
E026 - Custom validation command unsuccessful
Diffblue Cover was not able to execute the custom validation command successfully and has disabled test validation.
E027 - JUnit Jupiter Engine not found
Diffblue Cover was not able to find a JUnit Jupiter Engine configured in your project's dependencies. Diffblue Cover uses this to determine the version of the JUnit Jupiter Launcher to use when verifying tests. Please ensure that your project is configured to run JUnit Jupiter tests. Because of this, Diffblue Cover will not be able to verify tests.
E028 - Cannot determine dependencies
Diffblue Cover was not able to determine the dependencies of your project. Check the build system output in the user log file for further information. Because of this Diffblue Cover is not able to verify tests.
E029 - Invalid trace directory
Failed to select a trace from the trace directory. Please review the cause message to diagnose the underlying issue.
E030 - Test creation cancelled
Test creation for this method was cancelled as requested.
E031 - Unsupported Java language version
We recommend you change your module settings to Language Level 8, 11, 17, or 21.
E032 - Failing tests detected while validating
Diffblue Cover tried to validate the tests it created but failed due to failing tests. Diffblue Cover cannot fix this problem automatically. The output from running the validation command is available towards the end of the log file. Please see our documentation for further guidance.
E033 - JUnit Jupiter versions mismatch
Diffblue Cover discovered a mismatch in JUnit Jupiter Api and Engine versions. Please ensure that your JUnit Jupiter Api and Engine versions match. Because of this, Diffblue Cover will not be able to verify tests.
E034 - Running existing tests took too long
Diffblue Cover tried to run a command to run all the existing tests, but it took too long. The output from running the command is available towards the end of the log file.
E035 - Running existing tests failed
Diffblue Cover tried to run a command to run all the existing tests, but it failed. The output from running this command is available towards the end of the log file. While Diffblue Cover could not figure out the reason for this and cannot fix it automatically, this issue is usually due to an incorrect command, or due to the failure of existing, user-provided tests.
E036 - Existing test failures
Diffblue Cover tried to run all the existing non-Diffblue tests but failed due to failing tests. Diffblue Cover cannot fix this problem automatically. The output from running the validation command is available towards the end of the log file.
E041 - Failed to apply refactoring
Failed to apply refactoring. Check the build system output in the user log file for further information.
E042 - Failed to write refactoring config file
Failed to write refactoring configuration file. Please enable write permissions on this file and its parent folder.
E043 - Failed to install into Maven repository
Failed to install a file into the local Maven repository. Make sure the displayed command can be executed successfully.
E044 - Incompatible user options
The two given options are incompatible. Remove one of them.
E045 - Validation command failed for unknown reasons
Diffblue Cover tried and failed to validate the tests it created. The output from running this command is available towards the end of the log file. While Diffblue Cover could not figure out the reason for this and cannot fix it automatically, this issue is usually due to an incorrect validation command, or due to the failure of existing, user-provided tests. Please see our documentation for further guidance.
E046 - Failed to load Maven settings
Failed to load Maven settings.xml files from the user's home directory or maven installation directory. Make sure that Maven commands can be executed successfully, using your settings.
E047 - Unsupported Java version
Please use Java 8 Update 351+, Java 11.0.17+, Java 17.0.5+, or Java 21.0.1+.
E048 - Invalid JaCoCo report file
Diffblue Cover was unable to read the given JaCoCo report file.
E049 - inotify limit too low
The current inotify watch limit is too low. Try restarting the IDE and/or your machine. Check your inotify limit and consider resetting to a higher value.
E050 - Unsupported tool version
Unfortunately the version of the specified tool you are using is unsupported. Please consider upgrading.
E051 - Current JVM does not support JDK which compiled the project
Diffblue Cover needs to be executed with the same or a more recent Java version than the version with which the project was compiled.
E052 - Missing dependency
Required dependencies were not found. Please add these dependencies.
E053 - Unsupported dependency
A dependency was found at an unsupported version. Please upgrade it to the given version.
E054 - No class files found
Diffblue Cover could not find any .class files for your project. This usually means that your project has not yet been compiled.
E055 - Failed to compile a simple example test
For Diffblue Cover to run successfully, we require an example test to pass. Please see our documentation .
E056 - JDK not found
Diffblue Cover requires a JDK (Java Development Kit) to run. A JRE (Java Runtime Environment) is not sufficient. Diffblue Cover expects the JDK in
RT_JAR_PATH
or
JMODS_PATH
. Make sure a JDK is installed in these locations.
E057 - Analysis service, certificate issue
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). There was a problem with the SSL certificates used to set up the connection. Check whether you have the full set of CA certificates for Java installed.
E059 - Analysis service startup message timeout
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). Diffblue Cover did not receive the "port message" from the service before the timeout. If your machine is heavily loaded or very slow, try reducing load before running Cover.
E060 - Analysis service startup SSL issue
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). There was a problem with the SSL connection to the service. Please contact Diffblue Support , providing details about this error.
E061 - Analysis service startup timeout
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). Diffblue Cover did not receive the "alive message" from the service before the timeout. If your machine is heavily loaded or very slow, try reducing load before running Cover.
E062 - Analysis service JVM exited unexpectedly
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). Service failed to start due to a JVM issue. Please contact Diffblue Support , providing details about this error.
E063 - Diffblue Cover component missing
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). A Diffblue Cover component is missing. Please check your installation is complete.
E064 - Service startup I/O failure
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). Starting up the service failed because of an I/O problem while trying to execute the JVM for the service process. Please check whether your installation is complete, whether all files are readable and whether the JVM in JAVA_HOME is executable.
E065 - Analysis service, startup interrupted
Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). Please contact Diffblue Support , providing details about this error.
E066 - Dependency incompatible with JDK
Some dependencies are incompatible with the current JDK ( version ). Please add the following dependencies to your project ( list ).
E067 - JVM not a 64-bit implementation
Diffblue Cover requires a 64-bit JVM to run. A 32-bit JVM is not sufficient. Make sure a 64-bit JDK 8, 11, 17, or 21 is installed and
JAVA_HOME
is set to its installation location.
E068 - Failed to load custom input rules
Diffblue Cover tried to load custom input rules but was unable to read the content of the file correctly. Please review the content of the custom input file and ensure that it is correct. Information about the input rules format can be found in our documentation .
E069 - Environment checks failed
Please check your environment. More information on the runtime environment can be found in our documentation .
E070 - Compilation failed
Diffblue Cover cannot write tests because your project failed to compile. Please ensure that your project compiles successfully before trying to write tests again.
E071 - Surefire version mismatch
Diffblue Cover detected an old version of the Maven Surefire plugin in use in your project. Because of this Diffblue Cover will not be able to verify tests. Additionally, this version is not sufficient to produce coverage reports. Please upgrade the the most recent version. If you are using JUnit Jupiter 5, you need a minimum of 3.0.0-M7. If you are using JUnit 4, you need a minimum of 2.19.
E072 - Surefire missing
Diffblue Cover detected an old version of the Maven Surefire plugin in use in your project. Because of this Diffblue Cover will not be able to verify tests. Please upgrade the the most recent version. If you are using JUnit Jupiter 5, you need a minimum of 3.0.0-M4. If you are using JUnit 4, you need a minimum of 2.3.
E073 - Static mocking is not configured
The
--mock-static
option was specified, but your project has not been configured to use the Mockito inline mock maker. Mockito recommends placing the
mockito-inline
artifact where you are currently using
mockito-core
.
E074 - Mockito test dependency not found
The
--mock-static
option was specified, but Mockito is not present in your project. Please add Mockito to your project as a test dependency.
E075 - Static mocking is not supported
The
--mock-static
option was specified, but your version of Mockito is not sufficient to support static mocking. Please upgrade your version of Mockito to at least version 3.4.0.
E077 - Invalid trace file found
Unable to load the trace. Please record your application again with the Replay agent of your current installation of Diffblue Cover.
E078 - Writing report failed
Diffblue Cover tried and failed to write a report. Check to see if you have the correct permissions to write to the file, or use a different path for the report.
E079 - Failed to create test output directory
Diffblue Cover failed to create the test output directory (e.g.
src/test/java
). Make sure Diffblue Cover has the correct permissions to create a directory.
E080 - Invalid patch file
Diffblue Cover was unable to read the given patch file.
E081 - Failed to write file
Failed to write the coverage report. Please check permissions.
E082 - Could not find JaCoCo report
The JaCoCo report could not be found. To troubleshoot, try running the logged command and check that the coverage report is created at the expected location.
E083 - Error while producing JaCoCo report
The JaCoCo command failed for an unknown reason. Please check the user log file.
E084 - JaCoCo command failed
The JaCoCo command returned a non-zero exit code. Please check the user log file. This happens when there are no tests to run. If this is unexpected, make sure JaCoCo is setup in the project.
E085 - Attempt to compile a test as Groovy
Please ensure the build configuration compiles Diffblue tests as java.
E086 - Specified test framework not available
The test framework specified is not available on the classpath. Please add it as a dependency.
E087 - Multiple testing frameworks, select one
There are multiple testing frameworks available in your build configuration, and it is not clear which of them should be used by Cover. Please use the
--testing-framework
option to select a testing framework, e.g.
--testing-framework=junit-4
or
--testing-framework=junit-5
.
E088 - Android projects are not supported
Diffblue Cover cannot create tests for Android projects.
E089 - Can't parse specified test framework
The test framework argument provided is not a valid, supported JUnit version. Please refer to our documentation for the list of supported versions.
E091 - Failed to load execution policy rules
Diffblue Cover tried to load custom execution policy rules but was unable to read the content of the file correctly. Please review the content of the custom execution policy rules file and ensure that it is correct.
E092 - Missing embedded database engine
No embedded Java database engines were detected. This will prevent Diffblue Cover from writing tests for repository classes. Spring supports HSQL, H2, and Derby. Please add one of these as a dependency to your project. Alternatively, if you are not interested in testing repository classes, they can be excluded using the
--exclude
option.
E093 - JaCoCo plugin version outdated
The JaCoCo plugin version is outdated and can't generate coverage reports in the required XML schema (for use with Diffblue Cover Reports). Please edit your build file to update the JaCoCo plugin version.
E094 - jacoco-maven-plugin doesn't produce XML
The jacoco-maven-plugin is not configured to produce the XML output format. Please add XML to the list of <formats> in the configuration, e.g.