e2e-test-conventions
Pass
Audited by Gen Agent Trust Hub on Apr 15, 2026
Risk Level: SAFEPROMPT_INJECTION
Full Analysis
- [SAFE]: The documentation strictly prohibits hardcoding secrets and provides a template for using environment variables to handle credentials securely.\n- [SAFE]: The proposed environment configuration includes a mandatory check for the TEST_ENV variable, preventing accidental execution against production or unintended environments.\n- [SAFE]: Authentication state is managed through isolated storage files, minimizing credential exposure across different test projects.\n- [PROMPT_INJECTION]: The convention ingests data from external JSON files located in e2e/test-data/.\n
- Ingestion points: e2e/test-data/{feature}.json\n
- Boundary markers: Absent.\n
- Capability inventory: Playwright browser control and file system operations for authentication state.\n
- Sanitization: No sanitization or validation of the ingested JSON content is described in the conventions.
Audit Metadata