Create e2e test workflow #2911
Draft
Create e2e test workflow #2911
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
Rosie-Brigham
force-pushed
the
CHORE/add-e2e-workflow
branch
from
ba58301 to
0f51b71
Compare
Rosie-Brigham
force-pushed
the
CHORE/add-e2e-workflow
branch
from
e6a0c5f to
f7e250c
Compare
Rosie-Brigham
force-pushed
the
CHORE/add-e2e-workflow
branch
from
bad7832 to
d1dc797
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Adding an experimental GH actions workflow that runs on HMPPS runner that may be able to run our E2E tests, on any branch, without merging into main.
This is entirely experimental at this moment, and which may not work.
Planning to get playwite working first and then getting to cypress.
Alas, this has to be deployed to main to check wether it works, BUT once it does - we should not have to merge to main to run our e2e tests. 🤞 🤞🤞