Autosana runs your tests. agent-qa remembers what they proved.

Yes, and the reason is structural rather than a feature count. Autosana is a natural-language testing product where authoring and execution flow through the vendor's app, which means the asset you are building lives on their side of the line. agent-qa is a source-available QA agent with no paid tier, governed by FSL-1.1-ALv2: tests are plain-English YAML in your repository, runs execute on your laptop, in your CI, or from your coding agent, and every run writes back into memory committed beside the tests. The suite gets better at your app whether or not you renew anything.

Autosana is priced on vendor-set product subscriptions, so the bill tracks how much you test. agent-qa has no paid tier, no seats and no platform fee; FSL-1.1-ALv2 governs permitted use. You pay for the model tokens and infrastructure you already control, on the provider you choose, and the validated action cache takes roughly 60% of the tokens off a matched rerun. Adding coverage does not add a line item.

You are re-describing intent, not porting code, which is why this is far smaller than a normal test migration. Autosana flows are described in natural language already, so each maps one-to-one onto an agent-qa YAML test your team then owns in git. Run npx agent-qa init, write each critical flow as a plain-English YAML test, and let the runtime work out the selectors and the recovery. Most teams move a smoke suite in an afternoon, and there is nothing to un-pick later because the output is files in your own repository.

Yes, and from the same file. agent-qa runs end-to-end tests on web, Android and iOS with one natural-language format, one memory store and one evidence model, so a flow written once survives being pointed at another surface. Autosana covers mobile testing too; agent-qa's edge is that web and mobile share one repo-owned YAML contract, one memory store, and one CLI.

Yes, and identically in both. The same npx agent-qa run command executes on a laptop, in a CI job, or from a coding agent via MCP, with artifacts and memory written to the same repo-visible locations every time.