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.
E016 - Failed to determine project structure
Diffblue Cover was unable to detect the project structure due to an error when commands through the build system, details can be found in the user log file in .diffblue/log. Please run this command and ensure it completes without errors, or adjust the command in the DiffblueBuild.yaml file.
If you want to customise your build system configuration for Cover follow the guidelines here.
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.
E037 - Build config file could not be parsed
The supplied build system configuration file could not be parsed or validated.
E038 - Build system config file already exists
Could not save the build system configuration because the file already exists.
E039 - Build system config file I/O problem
Diffblue Cover was unable to read the build system configuration 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.
E076 - Custom build configuration invalid
There were problems validating the build system configuration.
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.
E090 - Non-compiling tests exist
Diffblue Cover cannot produce any coverage reports. This is due to some tests that failed to compile. These tests existed before Cover attempted to write tests. Please check the user log file and address the cause of the compilation errors.
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.
The XML coverage report is used by Cover Reports to show the coverage produced by Diffblue Cover alongside the developer written tests.
E095 - Project properties set to skip JaCoCo
Diffblue Cover has detected a jacoco.skip property is being set to true in the pom.xml of the project under test. To generate coverage, this value has been overridden. Please remove this property if this is unexpected.
E096 - Required file missing for upload
One of the report files was not available when we tried to upload them to Diffblue Cover Reports. This can be caused either by the reports not being created, or being moved before the upload started. See working with Cover Reports for more information.
E097 - Cover Reports server connection problem
We couldn't connect to the Diffblue Cover Reports server. This could be due to a wide number of reasons, for example:
Cover Reports isn't running, or the server is down
The Cover Reports hostname is not able to be resolved
There's a firewall blocking the connection between the machine and Cover Reports
The connection between the client and the server is too slow
If you were running as part of the create command you can use upload to avoid recreating all the tests. If you are still experiencing problems, please contact Diffblue Support.
E098 - Diffblue Cover Reports server error
The Diffblue Cover Reports server was not able to process the upload request. Please contact Diffblue Support.
E099 - Cover Reports upload was successful
The upload was successful.
E100 - Cover Reports upload was successful
The upload was successful.
E101 - Cover Reports upload status unknown
The upload was unknown because we didn't get a response from the server to indicate whether the upload was successful. Check your reports and see if the upload succeeded, if not, please try again. If you believe this is a problem, please contact Diffblue Support and provide this message along with the logs.
E102 - Cover Reports upload was successful
The upload was successful but the server sent a response we were not expecting. Please check your logs and contact Diffblue Support if you believe there is a problem.
E103 - Gradle project root not found
Diffblue Cover was unable to find the root of your gradle project. Check the user log file in .diffblue/log which contains the build system log to find the build system error messages.
E104 - Mockito failed to initialize
Mockito failed to initialize. This is usually caused by a mismatch between the version of Mockito and ByteBuddy. Please upgrade ByteBuddy to the version recommended in the Cover output code message. Cover will not be able to create tests using mocks until this is resolved.
E105 - No active Spring profile specified
This project uses Spring profiles, but no profile was defined via the --active-profiles option, therefore the default profile will be used. Use the --active-profiles option to explicitly specify the profiles to use. If a Spring profile named "test" was available, Diffblue Cover would select it automatically.
E107 - Incompatible Spring dependency
The dependency is not compatible with spring-core. Diffblue Cover may not be able to create Spring tests correctly. Consider upgrading your dependency.
E108 - Invalid method specification
Invalid method specifications were input by the user.
E109 - Max heap size too low
Diffblue Cover running without sufficient memory allocated. Please use the JVM_ARGS environment variable to increase the memory allocation.
E110 - Timeout running 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.
E111 - Credentials were not supplied
Authentication stopped while uploading coverage reports because password or username were not supplied. Please check your input arguments (--report-username and --report-password), or environment variables (DIFFBLUE_COVER_REPORTS_USERNAME and DIFFBLUE_COVER_REPORTS_PASSWORD).
E112 - Incorrect credentials
Authentication stopped while uploading coverage reports because username or password are incorrect. Please check your input arguments (--report-username and --report-password), or environment variables (DIFFBLUE_COVER_REPORTS_USERNAME and DIFFBLUE_COVER_REPORTS_PASSWORD).
E113 - Credentials were supplied but not needed
Authentication has not been enabled on your Cover Reports instance, so you do not need to provide a username or password. Please remove DIFFBLUE_COVER_REPORTS_USERNAME and DIFFBLUE_COVER_REPORTS_PASSWORD environment variables and --report-username and --report-password input arguments. Alternatively, you can enable authentication on your Cover Reports instance. See https://docs.diffblue.com/knowledge-base/diffblue-cover-reports/authentication/ for details on how to do this.
E114 - Unable to access project
The project asset was disposed. This is likely because your project configuration changed during an operation. Please rebuild the project and try again.
E115 - Incorrect JaCoCo coverage reported
JaCoCo reported incorrect coverage for a simple example class. Please check your JaCoCo configuration and ensure JaCoCo runs as expected on your system.
E116 - JaCoCo XML file missing
JaCoCo failed to create coverage for a simple example class. Please check your JaCoCo configuration and ensure JaCoCo runs as expected on your system.
E117 - JaCoCo coverage task failed
The JaCoCo coverage task failed. Please check your JaCoCo configuration and ensure JaCoCo runs as expected on your system.
E118 - JUnit Vintage Engine not found
Diffblue Cover cannot verify the generated tests because the JUnit Vintage Engine was not found. We have detected that you have dependencies on both JUnit 4 and JUnit Jupiter 5, however without the JUnit Vintage Engine, we will be unable to run any JUnit 4 tests.
Please ensure that your build system is configured to run JUnit 4 tests if you also have a dependency on JUnit Jupiter 5.
E119 - JUnit Vintage Engine incompatible
Diffblue Cover cannot validate the generated tests because an incompatible version of JUnit Vintage Engine was found. In order to run both JUnit 4 and JUnit Jupiter 5, we require a dependency on the JUnit Vintage Engine. This version should match the version of JUnit Jupiter 5 in order to successfully run the tests.
Please ensure that your build system is correctly configured to run JUnit 4 tests if you also have a dependency on JUnit Jupiter 5.
E120 - Git command failed
Please review git command failure and adapt accordingly.
E124 - JUnit Vintage Engine not required
Diffblue Cover has detected a dependency on JUnit Vintage Engine that is not required and may cause issues. Please remove your dependency to JUnit Vintage Engine. Alternatively, if you wish to also run tests in JUnit 5, please add a dependency to JUnit Jupiter Engine.
E125 - JUnit 4 incompatible with JUnit Vintage Engine
Diffblue Cover has detected a dependency on JUnit Vintage Engine which is incompatible with the version of JUnit 4 that we have detected.
JUnit Vintage Engine requires JUnit 4.12 or later to be present on the classpath. There is also a issue with JUnit versions 4.13.1 & 4.13.2 with JUnit Vintage Engine versions lower than 5.6.3 (junit5/issues/2198). In either case, this can mean that JUnit is unable to find any JUnit 4 tests.
E126 - Referenced file in patch file not found
Diffblue Cover was unable to find a referenced file in the patch file you have provided.
E127 - Construction mocking is not supported
The --mock-construction option was specified, but your version of Mockito is not sufficient to support construction mocking. Please upgrade your version of Mockito to at least version 3.5.0.
E130 - Invalid characters in template
The template must only use valid Java identifier characters (a-z,A-Z,0-9,$,_) and must not start with a digit. Remove the illegal characters.
E131 - Unterminated variable in template
The template contains an unterminated variable (${ without closing }). Fix this variable.
E132 - Invalid variable in template
The template contains an unrecognized variable. Remove this variable. In class templates only ${CLASS_NAME} is allowed. In method templates only ${METHOD_NAME} and ${INNER_CLASS_NAME} are allowed.
E133 - No variable in template
The template does not contain any variable to include the class or method name.
E134 - Only variable in template
The specified class name template consists only of the variable ${CLASS_NAME}. This would clash with the class under test. For example, try to add a suffix: ${CLASS_NAME}Test
E135 - Class name too long
The specified class name template has too much static text (more than 128 characters). This would probably lead to class file names too long to store on disk.
E137 - Mockito JUnit Jupiter is not configured
Diffblue Cover was not able to locate the Mockito JUnit Jupiter dependency. Please add this dependency to your project.
E138 - Unable to convert path to URL
Diffblue Cover was unable to convert the provided Cover Reports server path to a URL. Please check and update the server path and try uploading the reports bundle again. An example valid server path is https://reports.example.com:8080
E139 - Unsupported JavaEE version detected
An unsupported JavaEE version was detected. Please use JavaEE 8/JakartaEE 8 or JakartaEE 9.
E140 - Failed to communicate with GitLab
Diffblue Cover was unable to communicate with GitLab REST APIs. Please ensure that your access token details are correct and sufficient. The access token used must have access to the project with at least Developer role, and scopes including api, write_repository.
E142 - Sandboxing disabled
Information only
E143 - Failed to load class from custom rules
Diffblue Cover tried to load custom input rules, but was unable to locate the specified class(es). Please review and update the class path(s).
See Customizing test inputs for information about the input rules format.
E144 - Unsupported options
Don't use the --report-file, --jacoco-diffblue or --jacoco-manual options for multi-module projects. Use the --working-directory option to specify the module.
E145 - Failed to communicate with GitHub
Diffblue Cover was unable to communicate with GitHub REST APIs. Please ensure that your access token details are correct and sufficient. If a classic token is used, it must have the repo scope (Full control of private repositories). If a fine-grained token is used, it must have contents: write and pull requests: write permissions.
E146 - Test module skipped
Diffblue Cover skipped one or more modules as they contain test code only. Cover only writes tests for modules that contain "production code".
E147 - Unknown module
Unknown module was specified, please update the module name.
E148 - No modules selected
No modules were selected because all modules were excluded from processing. Please ensure that at least one module is selected.
E149 - Building project unsupported
Building projects is only supported with Maven and Gradle projects.
Please build the project manually before running dcover instead of using the build command.
E150 - Failed to build project
Diffblue Cover was unable to build the project under test using a standard Maven or Gradle command. Consider manually building your project rather than using dcover build.
E151 - Branch doesn't exist
Please check that the branch exists.
E152 - Spring Boot tests not enabled
Consider enabling spring-boot-tests.
E153 - Cover Reports server URL missing
Diffblue Cover was unable to find a valid Cover Reports server URL to upload to. Please check the URL you have provided and try uploading the reports bundle again.
E199 - Libraries with limited support found
Libraries are on the classpath that have only limited support by Diffblue Cover. For code that uses these libraries fewer tests may be written.
Last updated