Installation and setup
Java version mismatch when building a project
Java version mismatch when building a project
Your build tool may require a different Java version than what is currently active. Verify which version is active:Check what your project targets (e.g.
sourceCompatibility in build.gradle or maven.compiler.source in pom.xml) and ensure a compatible Java version is installed and selected. For example, a project targeting Java 18 needs at least Java 18 — but Java 21 works too.Update JAVA_HOME and PATH to point to the correct installation:Python version not detected or wrong version used
Python version not detected or wrong version used
Diffblue Agents uses the Python interpreter on your If your project uses a virtual environment, activate it before running the workflow:Diffblue Agents requires Python 3.9 or later. If you have multiple Python versions installed, ensure the correct one is first on your
PATH. Verify which version is active:PATH.Coding agent not detected
Coding agent not detected
Diffblue Agents requires a supported AI coding agent platform on your If the command is not found, install and authenticate the coding agent before running Diffblue Agents. Check the system requirements for supported platforms.
PATH and authenticated. Verify it is available:macOS: quarantine warning on first run
macOS: quarantine warning on first run
macOS may quarantine files downloaded from the internet. Remove the quarantine attribute:
Windows: scripts blocked from executing
Windows: scripts blocked from executing
Windows may block downloaded scripts. Unblock the required files in PowerShell:Restart your terminal after unblocking.
Server fails to start due to port conflict
Server fails to start due to port conflict
Another process is using the assigned port. Either stop the other process, or override the port:
"fetch failed" when using the CLI
"fetch failed" when using the CLI
The CLI cannot reach the Diffblue Agents Server. Check the port the server is running on from Then verify the server is reachable:If
.diffblue/server.json in your project root:.diffblue/server.json does not exist, the server is not running. A stale file (where the PID is no longer active) indicates the server crashed — restart the workflow.Licensing
License activation fails
License activation fails
Check the following:
- Your machine can reach
https://api.licensespring.comandhttps://licensing.diffblue.com. Check that firewall rules allow outbound connections to these URLs. - Your system clock is accurate. License validation is time-sensitive.
- The license key is entered correctly, including hyphens.
"quota exceeded" during workflow execution
"quota exceeded" during workflow execution
Your license quota (measured in additional lines covered) has been reached. The current workflow completes its in-progress work but does not start new partitions.Check your remaining quota:Contact your Diffblue account manager to discuss increasing your quota.
Workflow execution
Workflow fails during initial validation
Workflow fails during initial validation
The workflow checks that your project builds and existing tests pass before generating new tests. If validation fails:
- Java
- Python
- Verify the project builds:
- Maven:
mvn compile - Gradle:
./gradlew clean build
- Maven:
- Verify existing tests pass:
- Maven:
mvn test - Gradle:
./gradlew test
- Maven:
- Ensure JaCoCo is configured and Mockito is in your test dependencies.
- Fix any build or test failures, then re-run the workflow.
Tests are rolled back after generation
Tests are rolled back after generation
Diffblue Agents validates every generated test by compiling and running it. Tests that fail validation are rolled back automatically. This is expected behavior. The workflow summary shows how many tests were committed and how many were rolled back.A high rollback rate may indicate that the target code is difficult to test in isolation, or that the project has complex dependencies that affect test execution.
Cherry-pick conflicts reported
Cherry-pick conflicts reported
Diffblue Agents generates tests in a temporary worktree and cherry-picks committed tests back to your branch. If you made changes to the same files while the workflow was running, cherry-pick conflicts can occur.Resolve conflicts using standard git conflict resolution. The workflow reports which commits had conflicts.