agent-test:screenshot-protocol

Standardized screenshot protocols enforce a mandatory wait-before-screenshot sequence to stabilize the page state before capture, ensuring every action is properly named and traceable to its place in the test route.

A wait-before-screenshot protocol is a mandatory stabilization sequence required before capturing decision-point snapshots, ensuring the modern web application page state is fully loaded for reliable bug reports.

To name screenshots for traceable route reports in DFS exploration, apply standardized naming conventions for route, phase, and action, enabling easy navigation and strict screenshot-to-step correlation.

The minimum evidence set for automated QA testing includes baseline, action results, transitions, error states, and final state, balancing evidence quality and volume across modern web applications.

Yes, standardized screenshot protocols support error-state capture across modern web applications by defining a minimum evidence set and integrating with DFS-based route exploration to ensure full state visibility during testing.