Compare actual/expected screenshots in acceptance tests#124
Closed
Compare actual/expected screenshots in acceptance tests#124
Conversation
mattwynne
changed the title
7 tasks
Contributor
|
Picking this up in #382 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤔 What's changed?
⚡️ What's your motivation?
I think this package needs better tests so that we can confidently deal with edge-cases like #120.
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
We could also save off the rendered HTML - and compare that. I feel the diffs would be too hard to read and so not very useful. Might help for debugging though?
Or maybe it would be better to make specific assertions about the rendered DOM?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.