From an invitation to a real account.
QA.army’s first design partner has onboarded. We independently checked that the supplied account exists in production, is confirmed, and is enabled. This showcase captures that starting point.
A design partnership is an opportunity to shape the product around a team’s real testing needs. The next useful evidence will connect a specific saved Test to its executed Run and inspectable outcome.
Read the launch story →What is verified.
Publisher-verified summary · checked September 15, 2026 (Pacific time).
| Claim | Evidence |
|---|---|
| First design partner | Announced by the QA.army team for this launch. |
| Production registration | Verified. A matching account exists in production account records. |
| Account status | Confirmed and enabled at the time of inspection. |
| Registration date | September 15, 2026 (Pacific time). |
| Test and Run outcomes | No partner Run result is published in this showcase. |
| Business impact | No verified time savings, pass-rate, or ROI figures are published. |
Source: a read-only check of QA.army production identity records. This summary is published by QA.army; it is not an independent audit or a customer testimonial. Raw account records remain private.
Read the machine-readable proof summary →Read the evidence accurately.
Does a confirmed account mean a Test passed?
No. Account confirmation establishes registration status. A passing Test requires its own completed Run and evidence. We do not infer execution results from account status.
Where are the partner’s name, quote, and screenshots?
They are not included in this public release. No customer endorsement or private application content is implied by the onboarding milestone.
Can I inspect the product myself?
Yes. Open QA.army to start your own setup, or read the agent onboarding guide. Access to customer Workspaces and Runs remains private.
Start with your own critical journey.
Use your application URL and describe the behavior that must hold. Keep the result tied to the Test that ran.