Why a browser test can pass locally and fail in CI

A test passing on a laptop and failing in CI has at least two environments to explain. Start there.

Compare the app URL, browser configuration, viewport, locale, time zone, credentials and fixture state. Confirm that CI reaches the expected deployment. Look for shared records and background work that may complete at different times. Preserve the original failure’s screenshots and output before rerunning.

Then inspect the assertion. Is the test waiting for a meaningful application state, or merely assuming an operation has finished after a fixed delay?

Zerocheck records the environment, browser runner and exact YAML with each result. The local CLI can run on a development machine or CI runner; the hosted browser needs a reachable configured URL. Both paths use Zerocheck’s AI service, and CLI results and artifacts upload to the web app.

Choosing a local browser changes where it runs. The service connection is still required.

Read the GitHub Actions browser testing guide.