document requirements for e2e tests #235
Merged
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
deitch
force-pushed
the
e2e-tests-requirements
branch
from
bd92b0d
to
7481b22
Compare
deitch
force-pushed
the
e2e-tests-requirements
branch
from
7481b22
to
c294878
Compare
Closed
displague
approved these changes
Mar 23, 2022
Signed-off-by: Avi Deitcher <avi@deitcher.net>
displague
force-pushed
the
e2e-tests-requirements
branch
from
a0fcccc
to
15110ec
Compare
|
This is the way. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Document requirements for end-to-end tests. Currently, this is how I do the tests manually. With a clear list in a shared space, we should be able to plan towards automating them as well.