<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>QA The Other Way</title><link>https://blog.anytest.dev/</link><language>en</language><description>An engineering journal about QA when AI agents explore your app and write the tests. Concrete techniques, named trade-offs, primary sources.</description><item><title>More coverage, same QA team: a technical AnyTest capacity plan</title><link>https://blog.anytest.dev/posts/anytest-qa-team-capacity-roi/</link><guid>https://blog.anytest.dev/posts/anytest-qa-team-capacity-roi/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>A measured adoption plan for QA engineers and their bosses, with a benchmark protocol and transparent ROI simulations for teams of one, two, three and five.</description></item><item><title>A retry budget is not a repair budget</title><link>https://blog.anytest.dev/posts/retry-budget-not-a-repair/</link><guid>https://blog.anytest.dev/posts/retry-budget-not-a-repair/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>A test that passes on its second attempt still failed once. Keep that fact visible, price the repeated work, and give every flaky test an owner.</description></item><item><title>Keep the failure evidence before you rerun</title><link>https://blog.anytest.dev/posts/failure-evidence-before-rerun/</link><guid>https://blog.anytest.dev/posts/failure-evidence-before-rerun/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>The final screenshot rarely tells you how a test arrived there. Preserve the sequence, network context and assertion before another run changes the scene.</description></item><item><title>A separate browser is not a separate account</title><link>https://blog.anytest.dev/posts/separate-context-is-not-separate-account/</link><guid>https://blog.anytest.dev/posts/separate-context-is-not-separate-account/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>Browser contexts isolate cookies. They do not stop two tests changing the same server record. Give parallel writers distinct accounts and data.</description></item><item><title>A green checkmark is not proof</title><link>https://blog.anytest.dev/posts/green-checkmark-not-proof/</link><guid>https://blog.anytest.dev/posts/green-checkmark-not-proof/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>AI agents can now write your end-to-end tests. They inherit the oldest bug in testing: asserting on what is easy to see instead of what must be true. The fix is an independent oracle.</description></item><item><title>Your locator is a contract, not a coordinate</title><link>https://blog.anytest.dev/posts/locator-is-a-contract/</link><guid>https://blog.anytest.dev/posts/locator-is-a-contract/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>Generated tests love CSS paths and XPath. Those selectors describe where a button sat on the day the code was written, not what the button is. Here is the vocabulary that survives a redesign.</description></item><item><title>An agent with a browser needs a fence</title><link>https://blog.anytest.dev/posts/agent-browser-needs-a-fence/</link><guid>https://blog.anytest.dev/posts/agent-browser-needs-a-fence/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>A script cannot be talked into anything. An agent can. When your QA automation reads web pages, every page becomes a potential instruction source, and OWASP has a name for the attack.</description></item><item><title>What agentic QA actually saves, and what it costs</title><link>https://blog.anytest.dev/posts/what-agentic-qa-actually-saves/</link><guid>https://blog.anytest.dev/posts/what-agentic-qa-actually-saves/</guid><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><description>The honest ledger has three lines: authoring time you no longer spend, review time you now must spend, and repair time for the tests that rot. The savings are real when the first line beats the other two.</description></item></channel></rss>