Replies: 1 comment
-
Unfortunately I believe that there is no good solution to your problem. As you said - warnings in Cypress are not yet a thing, so that's off the table. The only other way to show messages would be in the terminal - but I think it's too easy to be omitted by the end user. So in the end - I think that your solution is the best way of handling this issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I wanted to use a warning mode that would let the test continue but show me the comparison issue nevertheless, but I could not find anything similar in the features. Also, I would like to delay comparing images to the end of testing and browse + accept/reject updates later. Then, re-run with error-like behaviour.
What does it do?
It issues an error/warning when the regression fails, does not fail the test, and offers later actions to perform (like full-replacement of the 'template' images).
Why do I need it?
Because Regression testing can break a lot, especially when the interface is modular and different deployments differ. I want the ability to compare such an interface against the 'original image' and consider whether changes are to be updated/accepted or whether the difference matters. I don't want to hide some UI elements since then the image does not capture the state well, elements can be hidden as a part of some other functionality, for example, so I wouldn't know whether the issue happens because the user has hidden the menu, since I would hide it every time.
It also makes the test continue in execution, so that difference in the image does not hinder the execution, which can be tiresome in text fixing.
Lastly, going and viewing all images one by one is too lengthy a process. I would welcome a page that would show a test headlines and image summaries on one place, which I could browse and validate at once. Possibly with something like 'update all image differences' button.
What did I achieve?
Warnings are (if I were searching correctly) not yet a thing in Cypress, though I saw some issues on this topic.
I make the tests continue with events
which displays the error,
but does not issue any warning so that one needs to expand all test bodies and inspect them :/ It is also not very robust since it relies on the message contents, which could be improved in some sort of feature.
Beta Was this translation helpful? Give feedback.
All reactions