Troubleshooting the IntelliJ Plugin

Structural issues with the project

Please ensure that you are using the IntelliJ plugin on a complete project, as the IntelliJ plugin is unable to run successfully if there are flaws in the project structure. Check that:

  • All modules in the project are configured correctly.
  • The project is compilable.
  • The Java SDK version is correct for your project.

Test directories

IntelliJ looks for an existing test source directory. If an existing test source directory cannot be found, it will create one and then notify the user where the tests have been created.


Error scenarios - inaccessible methods

If you are receiving spurious warnings about inaccessible methods, close IntelliJ and delete the .diffblue index file. By default, this file can be found in your home directory under .diffblue/index/projectname-hash, where projectname is the name of your IntelliJ project and hash is a unique identifier that Cover uses to disambiguate between projects with the same name. A new index is automatically created when the IntelliJ plugin is run again.


Error scenarios - inotify watchers

In Linux, Diffblue Cover uses the inotify(7) filesystem API to watch for changes to your class files. If you are receiving an error message about running out of inotify watchers, please follow the advice below to increase the number of watch handles:

  1. Add the following line to either the file /etc/sysctl.conf or a new *.conf file under the /etc/sysctl.d/ directory:

fs.inotify.max_user_watches = 524288

  1. Then run this command to apply the change:

sudo sysctl -p --system

  1. Finally, restart your IDE. You should now have enough watch handles for IntelliJ to successfully create your tests.

Uninstalling

Before beginning the uninstall process, please ensure that no test generation or assertion suggestion tasks are running.

results matching ""

    No results matching ""