The JADE 2022 release meets tomorrow’s business demands.
When the unit test runner executes a unit test and that unit tests raises an exception, currently the only information available is the exception number.
For many types of exceptions, additional information on the exception object (e.g. extended error text) can be critical to diagnosing the issue.
The suggestion is to add some way to display additional exception information to the unit test runner window - similar to the way the 'unexpected exception' window displays this information.
Guest
In the Unit Test dialog there is a menu item which will open the process.debug window on an exception, or an unhandled exception so you can inspect the exception object and navigate the callstack, its not the same but is likely more useful than just the extended error text from the exception.
in the unit test dialog there is a checkbox that will open the process.debug window when an any or unexpected exception occurs in a unit test