User Code Exceptions should Point to the Step in the Recording
When a test fails because of a RanorexException thrown by user code, the "Jump to item" in the report takes you to the *.UserCode.cs file, or displays a "file not found" error message if the user code comes from a code library. This is convenient for the user code developer but confusing for non-coding testers who want to see the test step which failed.
- The generated code for a recording step with an internal action starts with a "Report.Log" call. Add this line to user code actions too.
- Or Supply a function in the API that returns a RepoItemIndex with the current step number, which the user code can then supply to a Report.Log call.
- Make this depend on the log level (only if level >= Info), or do it for "Release" builds only.