You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI test: add HTTP response check for created site (#4000)
## Related issues
- Related to STU-1867
## How AI was used in this PR
Claude was used to write the code and explore the solution. The author
reviewed it manually.
## Proposed Changes
Follow-up to the CLI e2e tests in #3947. The `site create` test only
asserted persisted state on disk. This adds a real check: after creating
and starting a site, the test requests its homepage and confirms a 200
with HTML, so it now fails if a created site cannot be served.
This does not cover the custom-domain and HTTPS case, which cannot run
in an isolated, headless test. See the discussion in #3947.
## Testing Instructions
1. Build the CLI with `npm run cli:build`.
2. Run `npm test -- apps/cli/commands/site/tests/create.e2e.test.ts
--tagsFilter='e2e'` and confirm both tests pass.
3. Run the same with `--tagsFilter='!e2e'` and confirm the tests are
skipped, so the fast suite is unaffected.
## Pre-merge Checklist
- [x] Have you checked for TypeScript, React or other console errors?
0 commit comments