Skip to content

feat: Guided Tours E2E Tests#2415

Draft
camielvs wants to merge 1 commit into
06-11-feat_guided_tours_completion_metricsfrom
06-12-feat_guided_tours_e2e_tests
Draft

feat: Guided Tours E2E Tests#2415
camielvs wants to merge 1 commit into
06-11-feat_guided_tours_completion_metricsfrom
06-12-feat_guided_tours_e2e_tests

Conversation

@camielvs

@camielvs camielvs commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Description

This PR is 100% AI generated.

End-to-end tests that replicate and verify the exact flow of every guided tour, so a UI change that breaks a tour is caught here (and points at the tour + step to fix) rather than shipping a broken tour.

Rather than four bespoke specs, this is a single data-driven driver that reads each tour's real JSON definition and walks it the way a user would:

  • tests/e2e/tours/tourDriver.tsrunTour(page, tour) opens the tour, then for each step: asserts the step's spotlight anchor resolves in the DOM (the core regression signal), performs the gating interaction (or clicks Next for passive steps), and waits for the tour to advance (synchronised on the ?step=N URL the tour writes). It finishes on the completion step. A handler exists for every interaction type — drag-from-library, edge connection, task select, set-argument, undock/redock window, subgraph navigate/unpack, marquee multi-select, create-subgraph, and the full secrets flow.
  • Specs — one thin spec per tour: navigating-editor, first-pipeline, subgraphs, using-secrets. Each loads the shipped tour JSON via loadTour(...), so the test tracks the real tour and new steps are covered automatically (modulo a brand-new interaction type needing a handler).
  • eslint.config.js — teach playwright/expect-expect that runTour asserts internally.

Because the driver asserts each step's data-tour* anchor, removing or renaming an anchor a tour depends on fails the matching step by design.

The using-secrets spec exercises the no-backend path from #2405 / #2406: it fails the health ping and /api/secrets so the tour's in-memory mock backend serves the secret steps. The tour runs fully hands-on with normal gating, no /api/secrets calls fire, and the Submit Run confirm is asserted disabled (real run not wired in mock mode).

Related Issue and Pull requests

Closes https://github.com/Shopify/oasis-frontend/issues/644

Sits on top of the guided-tour stack (#2405 / #2406 and the framework/tour PRs below them).

Type of Change

  • New feature

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Test Instructions

  • pnpm test:e2e tests/e2e/tours/ — all four tour specs pass (run in parallel against a local dev server).
  • The using-secrets spec drives the no-backend path: it routes the health ping and /api/secrets to fail, so the tour's mockBackend activates and the in-memory mock serves the secret steps. It asserts no /api/secrets calls fire and that Submit Run stays disabled in mock mode.

Additional Comments

The centered tour popover overlaps a few dialog controls (Add Secret / submit confirm / the "Use Secret" lock button). The driver dispatches the click directly to those elements (clickThrough) so React's handler still fires — the only spot where it doesn't use a real mouse click.

@github-actions

github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown

🎩 Preview

A preview build has been created at: 06-12-feat_guided_tours_e2e_tests/f9ccfa0

camielvs commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator Author

Data-driven driver that walks each tour's JSON: asserts every step's
data-tour anchor, performs the gating interaction (or clicks Next), and
verifies advancement, finishing on the completion step. One thin spec per
tour (navigating-editor, first-pipeline, subgraphs, using-secrets).

The using-secrets spec drives the no-backend path: it fails the health ping
and /api/secrets so the tour's in-memory mock backend handles the secret
steps, runs them fully hands-on with normal gating, and asserts the Submit
Run confirm stays disabled in mock mode.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@camielvs camielvs force-pushed the 06-11-feat_guided_tours_completion_metrics branch from 586e87d to 6bffb2c Compare June 12, 2026 23:36
@camielvs camielvs force-pushed the 06-12-feat_guided_tours_e2e_tests branch from f7adb0c to f9ccfa0 Compare June 12, 2026 23:36
@camielvs camielvs mentioned this pull request Jun 13, 2026
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

#gsd:50583 Learning Hub

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant