Using the following test runner options, you can determine the action when an error is encountered whilst running each test case within the test suite:
- The
ignore-return-code:true option ignores any errors (based on a non-zero return code), and continues processing the next test case.
- The
-jit:core option produces a core dump file as each error is encountered, and continues processing the next test case.
- The
-jit:debug option invokes just-in-time debugging as an error is encountered, and only continues processing the next test case when you have closed the debugger.
- From within a test case, you can also call the CBL_DEBUGBREAK library routine, which invokes the just-in-time debugger.
As with normal COBOL applications that encounter fatal run-time errors, each run-time test failure is written to a debug log file. To ensure this information is captured if you encounter multiple failures, each error generates a
<test case-name>-mfdebug.log in the current directory.
In the case of procedural managed COBOL, to debug a testcase, you need to embed the CBL_DEBUGBREAK library routine in it in order to start the just-in-time debugger.
Procedural managed COBOL
To debug a test case, you need to embed the CBL_DEBUGBREAK library routine in it in order to start the just-in-time debugger.
Restriction:
- -jit:debug and
-jit:core are not supported with procedural managed test cases
