feat(testing): add reusable Playwright browser journeys - #170
Open
gbaudrit wants to merge 12 commits into
Open
Conversation
This was referenced Sep 11, 2026
Resolve resource-scope UI changes, renumber browser ADRs after current main, and isolate browser validation in its own workflow.
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
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
Adds the product-owned reusable Playwright foundation for #283 so Agentstration UX tests and communication captures share the same versioned journeys, explicit instance configuration, and campaign Workspace isolation. This PR is the baseline consumed by the dedicated
codex/playwright-application-coverageintegration branch and its child increments.Changes
browser-ux.ymlworkflow so the existing CI workflow remains unchanged.Validation
npm exec tsc -- --noEmit.npm audit --audit-level=highreported 0 vulnerabilities.maincompatibility gaps on this baseline: the managed model fixture registration and generated Flow handoff routes. Both are fixed in test(playwright): enforce application route coverage catalog #297, whose four managed .NET/Chromium smoke journeys passed before it was squash-merged intocodex/playwright-application-coverage.dotnetSDK.Breaking changes
None.