Forum Discussion
tristaanogre
12 years agoEsteemed Contributor
I would suggest first examining the error to determine why it failed. If it's a coding problem, keep the error.
If, however, it's a problem being reported as a problem with the application, that indicates, to me, that your handling of such errors within your automation needs to be addressed. I'd suggest using try/catch methodology for whatever script language you are using (available also in Keyword tests) to trap such errors and log them in whatever means you want.
You can also build into your tests such logic with "if <error condition occurs> Log.Warning" to customize how information is logged.
It's the difference, in short, between recording a test and playing it back... and building a test that actually is a test and not just a macro.
If, however, it's a problem being reported as a problem with the application, that indicates, to me, that your handling of such errors within your automation needs to be addressed. I'd suggest using try/catch methodology for whatever script language you are using (available also in Keyword tests) to trap such errors and log them in whatever means you want.
You can also build into your tests such logic with "if <error condition occurs> Log.Warning" to customize how information is logged.
It's the difference, in short, between recording a test and playing it back... and building a test that actually is a test and not just a macro.
Related Content
- 6 months ago
- 6 years ago