Repository navigation
Commit 375d3c9
docs(tests): document the LOCAL way to run the e2e suite
The docstring named only the deployed form, which reads as though an App Engine
deploy is required. It is not: these tests visit "/" and three static docs pages
and assert on titles, visible links and body text — no sign-in flow, no
datastore reads — so the docker-compose server the README already documents
serves them fine.
docker-compose up -d
pytest tests/test_e2e.py --base-url http://localhost:8080 -v
That turns an 18-test suite from "deploy first" into a fast local loop, which is
the useful shape when checking a dependency bump: the app either serves pages or
it does not.
Also records what the suite needs (pytest-playwright plus `playwright install
chromium`) and two honest caveats: the Sign In assertion depends on OAuth config
a local stack may lack, and the docs pages are static files, so a green local
run says nothing about whether the DEPLOYED docs are current.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G7y9rTA1r8r8EhEnPSQenR1 parent b4870b0 commit 375d3c9
1 file changed
Lines changed: 16 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | | - | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
3 | 5 | | |
4 | | - | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
5 | 11 | | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
6 | 20 | | |
7 | 21 | | |
8 | 22 | | |
| |||
0 commit comments