The previous setup asserted that the URL after submitting wp-login.php
matches /wp-admin/. On staging.peptiderepo.com, a login_redirect filter
sends successful admin logins to the site homepage instead of wp-admin,
so this assertion failed even on correct credentials — the setup logged
in, the storage state would have been usable, but Playwright treated it
as a credential failure and the storage state was never written.
Replaces the post-submit assertion with two safer checks:
- Wait until URL is no longer wp-login.php (i.e. login was accepted)
- Navigate explicitly to /wp-admin/ and assert we land there with the
admin bar visible
This bug was hidden behind the testDir misalignment (fixed in #1) and
the stale staging admin username GH Secret (rotated 2026-05-14). With
both of those fixed, the third bug surfaced.
Agent-Session: cto peptide-e2e-post-login-redirect-fix
When smoke.yml runs via workflow_call from another repo (peptide-repo-core,
peptide-starter-theme, etc.), GitHub Actions checks out the CALLER's repo
by default. The caller has no package-lock.json, so setup-node's npm cache
lookup fails with 'Some specified paths were not resolved'.
Fix: add repository/ref to the checkout step so we always fetch peptide-e2e
regardless of who calls the workflow. This ensures npm ci and Playwright
have the correct test code and dependency lockfile.
03-admin-plugins.spec.ts and 04-rest-api.spec.ts were cut off mid-test,
causing Playwright TypeScript parse failures and the smoke gate to show
0 jobs. Added the missing test bodies, assertions, and closing braces.
New tests added:
- PR Core Settings page loads (03)
- Peptide CPT verified via /wp-json/wp/v2/types/peptide (04)
Fixes smoke gate for all future deploys.
