This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
[WIP?] e2e test for selections. #141
Closed
Conversation
This file contains 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
|
Deploy preview for catwalk ready! Built with commit 5a80bb8 |
|
Yes we should use "flows" in the e2e tests (like user scenarios, eg first time user) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adding a simple test to verify that the selections are working.
I don't know if this is the way to go, every test takes something like 5 seconds so it will become quite slow.
We could test several things in one "run" (first verify the grid, then make some selections, then create a hypercube etc) but then the tests are not independent of each other, and a failure in one of the early "steps" would probably fail the later ones as well.