You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For continuous integration needs, I'm looking to include a hyperlink in the stack trace generated when a TestNG assertion fails. I haven't had much luck in finding this, including in rasing a Stack Overflow question that got zero responses.
Does TestNG have the ability to customize the stack trace that is generated when an assertion fails. From a general approach, it would be helpful to be able to specify a format for the file name shown in ths stack trace. Options would be to include file name only, file name with path, or file name generated as a URL.
Does anything like this exist in TestNG, or is there a straightforward path to customizing the stack trace at a different scope? I'd even be open to running sed on the output, which does not seem to be a straightforward task when the file name is included in the stack trace without any path information.
Thank you.
The text was updated successfully, but these errors were encountered:
For continuous integration needs, I'm looking to include a hyperlink in the stack trace generated when a TestNG assertion fails. I haven't had much luck in finding this, including in rasing a Stack Overflow question that got zero responses.
Does TestNG have the ability to customize the stack trace that is generated when an assertion fails. From a general approach, it would be helpful to be able to specify a format for the file name shown in ths stack trace. Options would be to include file name only, file name with path, or file name generated as a URL.
Does anything like this exist in TestNG, or is there a straightforward path to customizing the stack trace at a different scope? I'd even be open to running
sed
on the output, which does not seem to be a straightforward task when the file name is included in the stack trace without any path information.Thank you.
The text was updated successfully, but these errors were encountered: