gormes-browser-harness

Browser automation parity ensures consistent behavior for browser actions, CDP interactions, and browser connect workflows across different runtimes. You need to validate it when integrating new browser capabilities to confirm the same command surface and results across environments.

You validate browser automation parity by running a test suite that uses fake runners and fixtures to verify browser actions without launching real browsers. This checks alignment with public APIs and in-process runtime contracts across planning and validation workflows.

Yes, browser parity testing applies to CDP interactions, browser connect workflows, provider routing, and browser tool descriptors. It ensures consistent semantics and data formats across Hermes browser harness and the Gormes runtime environments.

Yes, browser harness parity checks provide reference guidance for browser providers, tool descriptors, and browser interaction skills. They align semantics and data formats to ensure consistent command surfaces across Hermes and Gormes runtimes.

Browser parity testing without real browsers relies on fake runners and fixtures to validate actions against in-process runtime contracts. It verifies command surface alignment and semantics but does not test real browser rendering or network behavior.