test(e2e): allow for manual triggering of E2E suite #24
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
|
Currently don't have a need for additional manual run controls for the E2E suites, so closing this. |
charliedmcb
deleted the
charliedmcb/allowForManualTriggerOfE2ETestSuite
branch
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.
Fixes #
Description
Currently there is no way to test within the github action workflows a new E2E test suite.
I'd like to be able to have it automatically pick up the change to the set of test suites and use that. However, the workflows are being run via their state on the
mainbranch. This solution is meant as an alternative solution by allowing a developer to trigger a e2e suite run, and then they can share the link within their PR description.How was this change tested?
Nothing additional
*
Does this change impact docs?
Release Note