Optimized for testing
Every decision is tuned specifically for QA - fewer false alarms, better reports.
Backed by
CombinatorEvery plugin update
CombinatorEvery plugin update
is a regression you didn't ship
Continuous QA for WordPress sites - contact forms, WooCommerce checkout, page builders. Catches the regression after every plugin and theme update, before your client's customers do.
[01] Skills & features
Bring your testing to another level
Forms, checkout, page loads. Replayed after every update.
PluginsThemesForms
Forms, checkout, page loads. Replayed after every update.
PluginsThemesForms
TRUSTED BY
[02] WordPress stack
Works with the WordPress
stack you already run
[03] The plugin gap
You didn't change anything
It broke itself
WordPress sites break between plugin updates, theme bumps, and page-builder edits you didn't make. The client doesn't care whose deploy caused it - they care that the contact form is dead.
Auto-updates don't ask for permission
WP core, plugins, and themes auto-update on their own clocks. Your client's site can break overnight without a single deploy from you - and the first person who notices is usually the customer who didn't get the email.
The form said success. The email didn't arrive.
Contact Form 7, Gravity, WPForms - all return 200 on submit. Whether the email actually arrives is a separate question, and nothing in your stack checks the answer. Lost leads don't file tickets.
WooCommerce checkout is a plugin chain
Cart plugin, payment gateway, tax plugin, shipping plugin. Each updates on its own schedule. Each can break the chain. The first signal is usually a chargeback or a client email.
You can't click through 30 sites.
Manual QA scales until your agency has 5 client sites. After that, you skip flows. After 10 sites, you skip whole journeys. After 30, you find out from the client's customer.
[04] Per-regression evidence
Every broken site, fully recorded
When a plugin update breaks a flow on a client site, you don't get a confused email. You get the recording, the step trace, screenshots, and the exact step that broke - so the fix is in motion before the client calls.
- 01Full browser session recording of the journey
- 02Step-by-step pass/fail breakdown of every action
- 03Screenshots captured at each key moment
- 04Clear bug report with reproduction context
- 05Slack, Discord, or email alert with all evidence attached
[05] How it works
Four steps to WordPress QA without the maintenance
Point us at the WP site, describe critical flows in plain language, and let TesterArmy run them after every plugin update - so you catch regressions before your clients do.
Connect GitHub
staging.yourapp.com
Create a project
Paste your WordPress site URL to set up a project. Works with WooCommerce, Elementor, Bricks, Oxygen, Astra, Yoast, and any plugin combination. No SDK, no test scripts, no infrastructure to maintain.
WordPressURLNo SDK
staging.yourapp
user@test.com
Submit
Write tests in plain English
Describe what to test in natural language. "Submit the contact form, check the confirmation page, verify the email arrives." No DSL, no SDK.
Natural languageNo SDKNo DSL
GitHub AppAuto on deploy
Production monitoringRecurring runs
WebhookAny CI pipeline
Run after every update
Trigger a journey run via webhook right after a WordPress core, plugin, or theme update lands. Or schedule recurring runs for continuous monitoring. Catches the regression before your client's customers do.
Post-updateWebhookSchedule
PassSearch results
Query returns the correct filtered items and pagination controls work as expected
Get a clear report
Get screenshots, recordings, and actionable bug reports on every run - from the dashboard, or routed to Slack, Discord, or email.
RecordingScreenshotsBug report
[06] Resources
TesterArmy in action
Explore real bug finds, QA tips, and client case studies from our work in practice.
August 26, 2026Introducing unbox-ai: See Where Your Agent's Tokens Actually Go
We built unbox-ai to read our own QA agent's traces. One command opens a token treemap, a latency waterfall, and a scrubbable timeline of the run. The same binary is a read-only trace explorer your coding agent can use. Now it's open source.
August 20, 2026Introducing the Issues Tab: One Row Per Bug, No Matter How Many Runs Found It
Agent-found bugs now land in one deduplicated list instead of scattered run reports. Every issue carries expected vs actual, repro steps, and a replay of the exact moment it broke - and leaves the list as a Linear ticket, a prompt for your coding agent, or resolved.
August 18, 2026We Benchmarked 10 Vision Models on Clicking What They See
All ten models answered every visual understanding question correctly. Grounding the click is where the field splits, and where GPT-5.6 Luna won on accuracy, precision, and cost.
[07] FAQ
Frequently Asked Questions
Yes. We test the rendered site in a real browser - the plugins, page builders, and themes under it are transparent to us. WooCommerce, Elementor, Divi, Gutenberg, ACF, and any custom theme all work the same way.
Yes. The agent fills the form, submits, and checks the confirmation. Our agent comes with its own inbox - plug it in as the recipient and the journey verifies the email actually arrives, not just that the submit returned 200.
Yes. Trigger a journey run via webhook after a WP core / plugin / theme update, or run on a recurring schedule. Catches the regression before your client's customers do.
When a journey fails, we send a message to your Slack, Discord, or email - with the recording, screenshots, step-by-step trace, and reproduction context already attached. Triage starts from evidence, not speculation.
Yes. Set up a project per client site. Each project keeps its journeys, credentials, and alert routing scoped to that client - so one agency dashboard covers 50 sites without leaking config.
Different layer. ManageWP and MainWP are dashboards for running updates and backups across client sites. Uptime monitors ping a URL and tell you if the page returns 200. TesterArmy walks the contact form, the WooCommerce checkout, the page-builder pages - and tells you when the flow that brings in leads or orders actually breaks. Use them together: they keep the site running, we keep it converting.
Auto-updates don't ask for permission.
TesterArmy watches anyway
Every plugin update might be a regression you didn't ship. TesterArmy runs the journeys your clients care about - contact, checkout, login - after every update and on a recurring schedule. The first signal of a broken site is a check, not a client email.
[08] Contact us