# Zerocheck blog

> Dated index of posts. Each entry is one HTML page; the product and documentation context is at https://tryzerocheck.com/llms.txt.

- 2026-04-10 [A browser pass is not a security review](https://tryzerocheck.com/blog/ai-code-security-review/): Functional verification and security review answer different questions about an AI-written change.
- 2026-04-09 [What should a self-healing browser test prove?](https://tryzerocheck.com/blog/self-healing-under-the-hood/): A replacement target needs evidence that the intended action and outcome stayed the same.
- 2026-04-09 [Turn “add a regression test” into a specific outcome](https://tryzerocheck.com/blog/postmortem-action-items/): A useful follow-up names the failure scenario, fixture and result the test must verify.
- 2026-04-07 [Meaningful locators are part of reliable browser testing](https://tryzerocheck.com/blog/playwright-ai-ecosystem/): Role, label and context help describe the intended control; an outcome assertion still does the real verification.
- 2026-04-07 [When a browser test stops earning its place](https://tryzerocheck.com/blog/deleting-e2e-tests/): Review a test’s purpose, failures and ownership before deleting it or keeping it by habit.
- 2026-04-02 [Automating browser execution leaves judgment with the team](https://tryzerocheck.com/blog/future-of-qa-roles/): The agent can repeat a flow; people still decide which outcome matters.
- 2026-03-31 [A browser run needs context to be useful evidence](https://tryzerocheck.com/blog/soc2-testing-gap/): Keep the test, environment and result together; compliance conclusions require a separate review.
- 2026-03-26 [Before moving a browser suite, isolate the cause of failures](https://tryzerocheck.com/blog/cypress-playwright-migration/): A framework migration can improve a workflow, but shared data and weak assertions can follow you.
- 2026-03-24 [Separate locator maintenance from changed requirements](https://tryzerocheck.com/blog/test-maintenance-burden/): A moved control, stale fixture and changed business rule need different fixes.
- 2026-03-17 [Coding agents can outpace your release checklist](https://tryzerocheck.com/blog/vibe-coding-testing-gap/): A faster implementation workflow needs a repeatable way to verify the customer journey.
- 2026-03-14 [Why a browser test can pass locally and fail in CI](https://tryzerocheck.com/blog/pass-local-fail-ci/): Compare the environment, fixtures and observed state before blaming the browser test.
- 2026-03-12 [What a skeptical developer should ask an AI testing tool](https://tryzerocheck.com/blog/ai-testing-skepticism/): Ask to see the failed test, the unchanged assertion and the evidence behind any healing.
- 2026-03-10 [The cost of a browser test nobody trusts](https://tryzerocheck.com/blog/flaky-test-economics/): Measure the work around a failure: investigation, reruns and the cost of ignoring the gate.

Updated: 2026-09-22