Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failure exceptiontype in output.xml #3673

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mkorpela
Copy link
Member

Based on discussions on #devel channel.

I got requirement that perform auto analysis on failures. I have did this but I felt if robot provide few info in error message this will help more in my task with high accuracy
Example: Let us assume test case consist keyword Should Be True "Demo" != "Demo1" and it got failed, we will get error message like "Demo" != "Demo1"
In above error message =! is my key and I update testcase analysis comment that its application issue since validation got failed.
Note: Accuracy may not be 100% but we have started and will improve this.
Here I need help from robotframework that, Let us have custom robotframework exceptions as prefix in error message
Example:

  1. Robotframework: If any Should * keyword got failed error message should be like ValidationException:
  2. Selenium: If any Wait * keyword got failed error message should be ElementException: <actual selenium throwed exception & error>
    So above approach gives confident on which type of error we got based on exception type and we can take a call on this.
    Note: This is draft idea and im not sure is this possible or not, is it valid?, how it helps robotframework, how other libraries owner react to it if possible.
    Since we are working on CI error message like showing error line number I have proposed this.

@adiralashiva8
Copy link

Implementation of #3674 issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants