What problem does it solve?
Changes to Streamlit's routing, auth, websocket, embedding, or asset-serving code can break externally hosted or embedded deployments (proxies, iframes, CSP constraints) even when local tests pass. This Skill reviews a branch or PR diff and decides whether external end-to-end coverage with @pytest.mark.external_test is warranted.
Core Features & Use Cases
- Eleven-category risk checklist: Evaluates routing, auth/cookies/CSRF, websocket transport, iframe embedding, static assets, service workers, cross-origin behavior, SiS/Snowflake runtime, client storage, and security headers.
- Any-hit decision rule: A single triggered category produces a "Recommend external_test: Yes" verdict with concrete diff evidence.
- Structured output: Produces a standardized recommendation with triggered categories, file-level evidence, suggested test focus areas, confidence level, and assumptions.
- Use Case: During PR triage, a reviewer runs this assessment on a diff touching Starlette routes and XSRF cookie handling, and receives a Yes recommendation with focus areas for iframe embedding and auth/session continuity checks.
Quick Start
Review this pull request diff and tell me whether it needs external e2e test coverage with @pytest.mark.external_test.