Skip to content

Add post-launch smoke test suite (npm run test:smoke) - #194

Draft
phpbits wants to merge 1 commit into
mainfrom
feature/manual-qa-automation
Draft

phpbits wants to merge 1 commit into
mainfrom
feature/manual-qa-automation

Conversation

@phpbits

@phpbits phpbits commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds npm run test:smoke, a Playwright version of the v1.1.0 post-launch manual smoke sheet (SM-01 to SM-16).

  • One test per case, in tests/e2e/smoke/post-launch-smoke.spec.js.
  • Separate config (playwright.smoke.config.js), so npm run test:e2e does not run it.
  • Runs in the wp-env tests environment. beehiiv is mocked by the existing test-only mu-plugin, and no email is sent. Each test checks the exact request sent to beehiiv, the saved WordPress state, and the editor or frontend UI.
  • Anything that needs a real inbox or beehiiv account carries a manual-only annotation. tests/e2e/smoke/README.md lists each one.
  • The suite activates twentytwentyfive if the tests environment has no valid theme, because the editor and frontend break without one.

Test plan

  • npm run test:smoke: 16 passed locally (about 4 minutes)
  • Run once in CI

Automates the v1.1.0 manual smoke sheet (SM-01 to SM-16) as Playwright
specs under tests/e2e/smoke with its own config. Runs in the wp-env tests
environment against the mocked beehiiv API. Cases that need a real inbox
or beehiiv account are annotated manual-only and listed in the README.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant