FAQ
DoesQA FAQ: no guesswork, just answers.
Everything you need to understand how DoesQA works, what it replaces, and how it helps you ship with confidence.
About DoesQA
What DoesQA is, who it’s for and how it compares.
What is DoesQA?
DoesQA is the most powerful codeless test automation platform for web products. Build real user journeys as Flows, run them in parallel on hosted browsers, and get Results with screenshots and video for every pass and fail. No coded framework to maintain.
See the docs overview.
Do I need to write code?
No. Flows are built from shared Test Steps in the Scenario editor and Flow Builder. Custom JavaScript is there for the rare edge case, and most teams never touch it.
More on the build model: Codeless vs coded.
Who is DoesQA for?
Teams that ship often and want strong end-to-end coverage without owning a second engineering stack for tests.
QA and automation testers who want speed and low maintenance
Engineering teams who want CI gates and real browser evidence
Leads who need email, MFA, APIs and branching journeys in one product
What tools would we still need alongside DoesQA?
Your unit tests, lower-level API checks, CI system and chat alerts. Keep them where they already earn their keep. DoesQA is the end-to-end layer: real browsers, real journeys, hosted Runs, and it plugs into your CI and chat tools.
Does DoesQA help if we already have good automated test coverage?
Yes. The hardest part is usually end-to-end: email, MFA, frames, payments, flake and runner ownership. DoesQA takes that layer off your hands without a rewrite of what already works. Coverage and speed.
What does DoesQA do that other tools can't?
Everything a coded stack makes you build yourself ships in one product: authoring, shared Test Steps, hosted runners, Results, email inboxes and MFA. Nothing to assemble.
Side-by-side example: DoesQA vs Playwright: the same test compared.
How is DoesQA different from Playwright or Cypress?
Playwright and Cypress are frameworks for writing browser tests. DoesQA is the full system teams usually end up building around them: visual authoring, runners, Results, and journey features included.
Is DoesQA just a wrapper around Playwright or Selenium?
No. DoesQA is the full stack: authoring, shared Test Steps, hosted runners, Results, schedules, and CI. A framework gives browser APIs; you still assemble the rest.
Is there vendor lock-in?
No. You can export your tests as usable code at any time, so your work stays yours. No lock-in.
When would you not recommend DoesQA?
When your main job is not browser end-to-end testing (for example native mobile as the primary surface, or a pure unit-test problem).
When the job is web journeys in a real browser, DoesQA is built for that. Codeless vs coded.
If DoesQA is so much better, why isn't everyone using it?
Most teams already invested in a coded stack, and switching felt expensive. Our free, team-led migration removes that cost.
More on the cost of ownership.
Is DoesQA really the best option or is that just marketing?
For end-to-end web journeys, DoesQA is the most powerful tool you can choose: low maintenance, Results you trust and everything included. For unit tests or native-only apps, use the right tool for that job.
Is DoesQA suitable for enterprise use?
Yes. Enterprise adds custom scale, SLA, NDA and security reviews, procurement support, and dedicated onboarding, on top of hosted Runs, Cyber Essentials certification and AI you can switch off.
How long does it take to get started?
Minutes. Add your site, build your first Flow and run it. Moving from a coded suite? Our team migrates it for free.
Can you migrate our existing tests?
Yes, free. Our team rebuilds your Playwright, Cypress, Selenium, WebdriverIO or other suite in DoesQA, and migration is fast: END. moved a 9+ month Cypress pack within days. Migration.
How does DoesQA help engineering teams ship faster?
Faster test creation, parallel execution, clear coverage and failure context, and less framework maintenance. Less time managing QA, more time shipping.
What problems does DoesQA replace?
Maintaining coded frameworks, managing runners, unclear failures, and stitching side tools together. You get one system instead of more overhead.
Do I need a QA team to use DoesQA?
No dedicated automation-engineering team is required. People with basic automation knowledge can build and maintain DoesQA. Many engineering teams own it directly.
What kind of companies use DoesQA?
From solo founders to Superdry, WPP and Bubble: teams that ship often and can't afford broken releases, including organisations that need UK hosting and strong security.
Product and testing
Flows, Runs, Results, AI, email and test data.
What types of testing can I do with DoesQA?
End-to-end testing of real user journeys in a real browser, including:
Login, MFA and email verification
Payments and checkout
APIs and UI in one Flow
Branching journeys, accessibility, visual, SEO and performance checks
DoesQA is the safety net for everything your users touch. See Coverage and speed.
Does DoesQA do visual regression testing?
Yes. Visual checks run in the same Flow as your functional steps, with stored baselines and history across Runs. Visual regression.
How much test coverage can DoesQA provide?
As much journey coverage as your product needs. If a person can do something in the product, your Tests should be able to do that too.
Measure coverage by real user journeys in the pack, not a tool scorecard. Coverage and speed.
What can I export?
Your tests, as usable Playwright, Cypress, Selenium or WebdriverIO code. It's your exit path, and you own it.
How reliable are DoesQA tests?
Green means it works. Red means something real broke. Flows, Steps, runners and Results are one platform, and every customer runs the same proven Steps.
Does DoesQA produce flaky tests?
No. DoesQA is flake-free by design. With automatic waiting, fixed Selectors and human-approved Selector updates, a red Run means something real broke, not something to rerun until green.
How does DoesQA reduce flaky tests?
By removing common causes:
Shared Step behaviour instead of custom test code bugs
Fixed Selectors with a person in the loop (no silent self-heal)
Hosted runners in the same product as the Tests
Clear Run evidence so teams can stop on red
How much test maintenance does DoesQA require?
Very little, and it doesn't grow with your pack. Update a shared Element, Step Group or Flow Branch once and every Test Case that uses it follows. Maintenance is at least 400% faster than coded frameworks for the same journeys.
How quickly can DoesQA run a regression suite?
Fast. Test Cases run in parallel on hosted runners, so a pack finishes in the time its slowest journey needs. 935 Tests run in under 30 minutes.
Can DoesQA run in CI/CD?
Yes. Trigger Runs from GitHub, GitLab, Bitbucket or Azure DevOps, on a schedule or on demand. Results come back as Checks on your PR, with alerts in Slack or Teams.
Do tests run in parallel?
Yes. Test Cases run in parallel on hosted runners so large packs finish faster. Concurrency depends on your plan.
What is a runner?
A runner is parallel execution capacity: how many Test Cases can run at the same time. More runners means faster feedback.
Do I need to manage runners or infrastructure?
No. Execution is fully managed inside DoesQA. No browser farm to build and no third-party remote runner to argue with.
Can DoesQA test email registration, verification, and password reset?
Yes. DoesQA includes built-in test inboxes and Mail Test Steps. Enter $testEmail in your application, wait for the message, open it, and follow links in the same Flow. Guides: Email testing in DoesQA, Registration and verification, Forgotten password.
Do I need a separate email testing service with DoesQA?
No. DoesQA supplies Account and Test Case inboxes inside the product. Each Test Case Run can use its own $testEmail address so parallel tests stay isolated. External mail APIs are for teams wiring coded frameworks; DoesQA covers wait, open, click, and assert in the Flow.
Can DoesQA test passwordless or magic-link login?
Yes. The same Mail pattern applies: request the link, wait for email, open the message, and touch the sign-in link. See Passwordless login.
Can I inspect emails after a test finishes?
Yes. Open Mail in the DoesQA app to review Account or Test Case inboxes while you build, or after a Run to see what arrived during the test.
Can DoesQA generate fake user data for forms?
Yes. Built-in Values such as $testFirstName, $testLastName, $randomNumber, and $testEmail generate realistic data when you type $ in supported fields. Built-ins are native to DoesQA. Guide: Test data in DoesQA, Built-in Values.
Does DoesQA have a Value Store?
Yes. Account Values under Assets → Values hold shared config. During a Run, Data steps and API responses write to the Value Store so later steps can read the same names. Guide: Value Store, Test data in DoesQA.
Can DoesQA call APIs to set up test data?
Yes. Integration steps (GET, POST, PUT, PATCH, DELETE) run in the same Flow as your UI steps. Store the response and reuse fields in later steps. Guide: Test APIs in a Flow, Seed and clean up with API steps.
Do I need an external mock service with DoesQA?
For APIs you own, seed data with Integration steps against a test environment. When a dependency needs canned HTTP responses, store the mock base URL in a Value and call it from Integration steps. DoesQA integrates cleanly with mocking services you already run. Guide: Use mock servers with DoesQA.
How does DoesQA prepare test data for UI journeys?
Built-in Values fill forms. Account Values hold shared URLs and secrets. Integration API steps create and verify backend state in the same Flow as the browser. The Value Store carries captured data through the Test Case. Guide: Test data in DoesQA.
Pricing and plans
Trial, usage, support and upgrades.
Why pay for DoesQA when Playwright is free?
Because Playwright is only free to download. The expensive part is everything around it: runners, mail helpers, reporting, flake, and the people who keep that system alive.
DoesQA puts that in one product. The Real Cost of Playwright · DoesQA compared.
How does the trial work?
Every plan starts with a 7-day trial, with full access to everything in that plan. No setup required, so you can start testing straight away. A cardless trial is also available.
Will I be charged during the trial?
No. Cancel anytime before the trial ends and you won't be charged.
How many parallel runners are included?
Starter includes 10 parallel runners, Growth includes 25, and Pro includes unlimited parallel runners.
What counts as a test step execution?
A test step execution is counted each time a billable step in your test runs. Only steps that actually run count, and Starter and Utility steps are never counted.
Why does DoesQA charge by test step?
Because it scales with what you actually run. You never pay for idle seats or empty runners.
What happens if I exceed my included usage?
With auto-upgrade enabled, DoesQA can move your account to the next plan as usage grows. Pro accounts can continue beyond included usage, with additional step executions at the overage rate.
Can I upgrade or downgrade later?
Yes. Move between plans as your requirements change. Auto-upgrade can move you up as usage grows when enabled.
Can I cancel without talking to sales?
Yes. Cancel anytime, fully online. No calls required.
What support do I get?
Real help from real experts on every plan: Amazing Support on Starter, Priority Support on Growth, and direct Slack or Teams support on Pro. Free migration support and hands-on troubleshooting are included. Get help.
Security and data
Hosting, compliance and how we handle your data.
Does DoesQA train AI models on customer data?
DoesQA AI runs inside DoesQA, hosted in the UK. Learning is optional. When it's on, other customers only ever get generic learning, never your private account detail. You can switch AI and Learning off at any time.
Is DoesQA secure?
Yes. DoesQA runs on AWS in the UK (eu-west-2) with encryption at rest and HTTPS for customer access. Cyber Essentials certified, proven 99.9% uptime, and approved for use by the UK Government.
How does DoesQA handle credentials and secrets?
Store passwords, tokens and MFA secrets as Private Values. Once saved, they stay hidden in the UI and never need to appear in plain step text.
Can DoesQA safely test production systems?
Yes, with care. Staging is best for full regression. Many customers also test production with careful URLs, Values, IP allowlists and blocked hostnames.
Where is my data stored?
Infrastructure runs on AWS in the UK (eu-west-2). DoesQA LTD is registered in England and Wales.
Does DoesQA store our data?
Yes. DoesQA stores only what you provide for testing: Flows, Elements, Values, Run evidence (results, screenshots, video), and account settings. Run evidence is retained for 60 days. Account assets stay while the account is active.
Is DoesQA GDPR compliant?
Yes. DoesQA is UK GDPR compliant, with UK hosting and full GDPR rights, including removal.
What happens to my data if I cancel?
You keep everything. Flows, reports and Elements stay in your account unless you ask us to delete it, and you can export your tests at any time. New Runs stop when your plan ends.
Get your next release tested end to end.
Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.