Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability, but it is not intended for production use and is not supported as such. Furthermore, Micro Focus does not guarantee that this feature will be delivered at a GA level and if it is, then the functionality provided might differ considerably from this technology preview. During the preview, you are encouraged to share your feedback and experiences via the Micro Focus community forum -
http://community.microfocus.com/microfocus/).
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
