The CONTINUE_ON_FAILURE feature is nice, but it is very hard to find out which step failed if the test steps are dynamic, especially if they are within a subprocess/method call. After the test is completed, the log viewer should show the traceable failure just like STOP_ON_FAILURE does, so the user can drill down and see the actual flow the failed. Currently, all of the steps show Passed, but only the test case shows failed, so I can’t tell where the failure occurred.

Tested on 5.3.1 and 5.4.