-
Notifications
You must be signed in to change notification settings - Fork 28
Exceptions
Home -> User Guide ->
This document was last updated on February 11, 2021.
The Generator caught an IOException trying to read the Cobol source file while merging a test suite with the source file.
There was a problem processing the command line arguments passed to the tool. The associated message provides more information.
When creating or loading the concatenated test suite file based on multiple test suite input files, an IOException was caught. The cause may be a lack of write permission on the file or a directory in its path, limited space on the output device, or another output file related condition.
The input files(s) or stream(s) for test suite input contained no data.
The config file does not contain an entry that is necessary for correct functioning of the application. The exception will have a message that identifies the path to the config file and the key value it's looking for (message INT002).
The Config class caught an IOException while trying to load configuration settings from config.properties. The cause is the IOException.
A test suite file specified in the configuration setting test.suite.path or on the command-line option --test-suite-path was not found. The filename may have been mis-keyed or the file may not be located where specified.
This exception is not supposed to be seen by users. It indicates an internal logic error in the application code. It is intended to help with debugging and to provide early warning during testing that we have "broken" something, and assistance with tracking down the cause.
If you get this exception "in the wild," please create an issue.
The application is in an illogical state for some reason. Usually, code has detected a null reference via an if statement or a catch block in a place where null references are not supposed to occur. The tool checks for this as it runs to guard against logic errors getting released, in particular NullPointerException, as that is characteristic of Java. It is also thrown when the tool detects that actions are being taken in the wrong order, and the result cannot be correct. Both these general types of errors are possible when we make changes to the code.
The accompanying message will provide additional information to narrow down the place in the code where the error was detected, and to provide developer-friendly guidance as to how to approach a solution, above and beyond what one might glean from the stack trace.