From a5ac3bc826249893d5c5f7389416a4f64778e366 Mon Sep 17 00:00:00 2001 From: razazarif Date: Wed, 4 Nov 2026 10:56:01 +0500 Subject: [PATCH] ci: run the nav.json portal tests Adds the v4-test-automation nav.json step (pnpm test:nav:visual) after the visual step. Each scenario generates its own petstore copy with this build of the CLI, three at a time, and checks the tab bar and sidebar against baselines. Adds ~5 min to the job. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/portal_tests.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/workflows/portal_tests.yml b/.github/workflows/portal_tests.yml index 59f23579b..b3b9bd85c 100644 --- a/.github/workflows/portal_tests.yml +++ b/.github/workflows/portal_tests.yml @@ -166,6 +166,17 @@ jobs: PLAYWRIGHT_BROWSERS_PATH: ${{ github.workspace }}\.playwright-browsers run: pnpm test:visual + # The nav.json layouts that build. Each scenario generates its own copy + # of the suite's petstore build with this CLI and serves it on its + # worker's port (8090-8092), three at a time, so this needs neither the + # generate step above nor its server, and runs even if they failed. + - name: visual — nav.json + if: ${{ !cancelled() }} + working-directory: tests + env: + PLAYWRIGHT_BROWSERS_PATH: ${{ github.workspace }}\.playwright-browsers + run: pnpm test:nav:visual + # Functional runs against the suite's auth build, whose playground calls # the API Tester (tests/api-tester/) on localhost:3000. # Playwright starts the API Tester itself (webServer in playwright.config.ts),