niwashi-smoke-test

Automated smoke tests for React narrative visualizations are performed using agent-browser to verify rendering, detect console errors, and validate interactions across all narrative sections. The test requires a running dev server and a sections-checklist.json with review_approved set to true.

A browser smoke test for narrative visualizations is an end-to-end verification process that checks if all sections render correctly, no console errors occur, and interactive elements function as intended using agent-browser. It serves as a post-review quality gate for React-based narratives.

Yes, agent-browser is used to check for console errors in React narratives by executing an end-to-end smoke test that validates rendering, monitors console stability, and verifies interactions. This ensures the completed narrative visualization functions without runtime errors.

Yes, a running dev server or a buildable project is required to perform end-to-end UI testing on narratives. The smoke test uses agent-browser to interact with the live application, requiring the server to be active to verify rendering, console stability, and interactive elements.

A smoke test on a completed narrative visualization should be run during post-review quality gates after the sections-checklist.json has review_approved set to true, or as a standalone QA verification step to ensure all sections render correctly and interactions work without console errors.

Narrative smoke testing with agent-browser is limited to React-based narratives created within the niwashi workflow and requires a sections-checklist.json with review_approved set to true. It cannot verify narratives lacking a running dev server or those built outside this specific workflow.