Make the caller own its SUT lifecycle and use the versioned action - #1
Merged
Merged
Conversation
E2E test report
|
omermorad
changed the title
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
1 participant
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.
Summary
The starter workflow starts and waits for its example SUT, calls the URL-only action, then collects logs and tears down its own services. The action no longer manages application infrastructure.
Release dependency: do not merge yet
Implementation: codotech/playwright-e2e#14
Currently v0 points to v0.2.0 and still requires Compose in the action. This starter cannot pass against that version until the URL-only implementation is released under the selected version tag. No tags were published or moved.
Verification
Caller-workflow gate and comment tests pass in the action repository. YAML syntax, local documentation links, and whitespace checks pass. The URL-only implementation passed 36 offline checks and a 3-test real container smoke run before the consumer reference changed to v0.