Output Codes
Last updated
Was this helpful?
Last updated
Was this helpful?
Diffblue Cover performs a number of checks before, during, and after creating unit tests. First, general high-level checks are performed to make sure the basics are covered: development environment, license, and high level code testability. If everything looks good to go, then tests are created and code checks are performed during this process to highlight any issues. Finally, once tests are finished, they are validated to ensure they run without any issues.
Cover can generate a range of output codes during these checks to provide general information and highlight any issues. Details for all output codes are provided in the topics below. Note that as and when these output codes are displayed within Cover CLI and Cover Plugin, additional specifics may also be provided, if relevant.
We've also provided a number of "" topics here - these provide specific output code details to help resolve issues.
- Failed to start up analysis service
- Analysis service issue
- Attempt to compile a test as Groovy
- Unable to load class
- Static initializer failed
- Failed to instantiate class under test
- Sandboxing policy violation
- JNI sandbox policy violation
- No inputs found that don't throw a trivial exception
- Failed to create Spring context
- Method may be time-sensitive
- Tests discarded during validation
