Frequently Asked Questions
- Eclipse terminates unexpectedly or an Out of memory error is shown in Ant/Batch mode
- Two identical test sessions after using the Live Notification feature
- Report Generation: "[ERROR] Index file could not be created" using CLI.
Eclipse terminates unexpectedly or an Out of memory error is shown in Ant/Batch mode
This usually happens when the Java VM heap is full but additional memory still needs to be allocated. You need to increase the maximum heap size of the Java VM (e.g. launch your Java VM with the commandline option to set the maximum heap size to 512 MB: -Xmx512m). To change the maximum heap size when using Eclipse, open the file eclipse.ini in your Eclipse installation directory and look for an entry which starts with -Xmx... and increase it's value to e.g. 512MB by changing it to -Xmx512m.
Two identical test sessions after using the Live Notification feature
This most likely occurred after using the Live Notification feature on your local machine and pressing the "Download Coverage Log File" button. The download of the generated coverage log file is only necessary when the system you are testing with CodeCover is executed on another machine, e.g. in the case of a web application. If the tested system is executed on your local machine, it is not necessary to download the coverage log file, since it's location is known and entered into the test-session container automatically.
Report Generation: "[ERROR] Index file could not be created" using CLI.
This usually happens when some of the folders given in the destination parameter of the report command do not exist. This failure behavior is intended, since the user could have made a typo.
