Verification engineering and CI bottleneck is a hot topic right now.
Existing paradigms shifted:
- diffs matter less, outcomes matter more
- reviewing means examining outcomes, not diffs
- rich artifacts like rich traces, network logs capture in isolated environment enable effective iteration
1/5
E2E tests break for two reasons: the product broke, or the test went stale.
Most frameworks can't tell the difference. So teams either burn hours triaging or start skipping tests.
We built @ShiplightAI to tell the difference. It's open to everyone today.
This is the best part about being a QA Engineer
It does not matter how the product gets built. Quality Assurance process and discipline will still be required
Even when that QA process and discipline evolves, we will still be required
It’s extremely exciting
AI writes tests that pass for the wrong reasons.
Issue 17 of AI in QA covers the shift from framework debates to agent-driven testing. Apple's Safari MCP server, CLAUDE.md guides for test suites, and 14 more.
https://t.co/iJCl3NQPb0