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
It'd be nice if a comparison between the expected and the actual value would be included in test failure messages for all assertions. So far I'm missing this for equal and equalRaw and noticed that it's already provided for documentCount, I didn't make a listing at the time of writing this issue.
There needs to be a concept/decision made about overlong actual and expected string values. I guess the first step could be truncation from the beginning, follow-up could be an excerpt of the start of the first mismatch plus a bit of offset to make it easier to find.
The text was updated successfully, but these errors were encountered:
Can you give me an example of what you are missing?
All the validator have and Actual, Expected and some also have a Diff listed.
Based on the other questions, i do notice that the Diff can be better explained, but if you have better ideas to improve the errorhandling i'm open for suggestions.
It'd be nice if a comparison between the expected and the actual value would be included in test failure messages for all assertions. So far I'm missing this for
equal
andequalRaw
and noticed that it's already provided fordocumentCount
, I didn't make a listing at the time of writing this issue.There needs to be a concept/decision made about overlong actual and expected string values. I guess the first step could be truncation from the beginning, follow-up could be an excerpt of the start of the first mismatch plus a bit of offset to make it easier to find.
The text was updated successfully, but these errors were encountered: