Raise User Defined Error for Assertions
Hello,
When assertions are encountered, the error contains a message describing the expected result vs actual result.
This is usually enough for the person who is writing the test since he knows what the expected response is.
Example: If you are expecting0 and got 1 , the person writing the test will know the issue and how to debug.
However, when I overtake someone else's project, I find their assertions very vague and they don't really make sense.
It would be cool to have a optional 'User Defined Assertion Message' window Which would make reading assertions much more QA friendly when they are encountered.
So in our example if we could have specified 'User Defined Assertion Message' as 'A non-zero error code signifies that the account is locked', this would be helpful.
Thanks
Ali
When assertions are encountered, the error contains a message describing the expected result vs actual result.
This is usually enough for the person who is writing the test since he knows what the expected response is.
Example: If you are expecting
However, when I overtake someone else's project, I find their assertions very vague and they don't really make sense.
It would be cool to have a optional 'User Defined Assertion Message' window Which would make reading assertions much more QA friendly when they are encountered.
So in our example if we could have specified 'User Defined Assertion Message' as 'A non-zero error code signifies that the account is locked', this would be helpful.
Thanks
Ali
