Droids launches Automated QA with /install-qa, browser flows, and PR reports

• Factory shipped Automated QA inside Droids, and FactoryAI's launch post frames it as a fix for regressions that pass tests and linters but still break in actual UI use.
• According to FactoryAI's feature description, the QA skill drives the app like a real user through login, navigation, form submission, and on-screen checks.
• FactoryAI's thread says each run captures screenshots, traces, and logs, then turns them into a QA report attached to the PR.
• Setup is command-based: FactoryAI's instructions says teams run /install-qa once to generate a project-specific QA skill, then /qa to execute tests.

Factory packaged browser-style regression testing as an agent workflow instead of a separate test harness. You can watch the launch demo video, read the official announcement, and inspect the exact setup flow in FactoryAI's command post.

Factory's pitch is straightforward: the missing layer is somebody actually clicking through the product. In FactoryAI's launch thread, the company describes Automated QA as a browser-driven check that exercises the app the way a user would, not just the way unit tests and linters do.

The behavior list in FactoryAI's feature description is concrete:

• log in
• navigate through the app
• submit forms
• verify that expected UI elements appear

The output is not just pass or fail. FactoryAI's thread says each run collects screenshots, traces, and logs, then produces a full QA report on the PR.

That makes the feature look closer to a built-in review artifact than a hidden background check. Factory's official post positions it as one piece of a broader Droids workflow that already spans code generation, review, testing, and deploy.

The activation path is two commands, according to FactoryAI's setup post:

1. Run /install-qa in a Droid session.
2. Let Droids analyze the codebase, ask about environments and critical flows, and generate a QA skill tailored to the project.
3. Run /qa to execute the test flow.

That project-specific setup step is the new detail buried in the thread. Factory is not shipping a fixed canned test suite, it is generating a QA skill from the repo and the team's own critical-path answers.