You describe
Write a test case as plain-English steps and an Expected Outcome. For example: search the Toolshop for hammer, and expect every result to be a hammer.
Documentation
Testmode is an AI testing tool for web apps. You describe a test in plain English, and Testmode runs it in a real browser, with no test scripts and no changes to your code.
Tests run in a cloud browser, so the app you test must be reachable from the public internet. Testmode tests web apps only, not native mobile apps, desktop apps or APIs.
How it works
Section titled “How it works”Testmode runs
Testmode opens your environment in a fresh cloud browser, logs in first when the test has a login credential, and works through your test.
You read the verdict
Each test ends Passed or Failed, with a written summary and a screenshot after every browser action the agent took.
Start here
Section titled “Start here”New to Testmode? The quickstart takes you from sign-up to your first result on a public practice shop, so you don’t need your own app yet: create your account and first project, write a test case in plain English, then run it and read the result.
Quickstart: run your first Testmode testOne guided path from sign-up to a first result.
What you can do with TestmodePlain-English tests, automatic login, evidence, schedules, Explore and the Assistant.
What Testmode can and cannot testA candid fit check: reachable URLs, login, CAPTCHA, iframes and more.
A tour of the Testmode appThe sidebar, project switcher, Overview and command palette.
Browse by area
Section titled “Browse by area”ConceptsHow a test runs, how organizations and projects fit together, and what Testmode records.
Account and teamSign in, invite people and understand the four roles.
Project setupEnvironments, login credentials and variables.
Test casesWrite steps and an Expected Outcome that the agent can follow.
Test plans and schedulesGroup test cases, run them on a schedule and email the results.
Runs and resultsStart runs, then read verdicts, screenshots and browser logs.
ExploreLet the exploratory agent visit your app and propose tests.
Credits and billingWhat a run costs and how your organization's balance works.
Popular tasks
Section titled “Popular tasks”Write effective stepsWording the agent follows reliably, with before-and-after examples.
Run testsChoose an environment and run one test, a plan or every enabled test case.
Schedule test plansRun a plan hourly, daily, weekly or monthly.
Understand run and test statusesWhat Queued, Running, Passed, Failed and Skipped mean, and why a test waits.
Log in automaticallyStore a test login once and reuse it across tests.
Use keyboard shortcutsOpen the command palette, start a run and move between pages.
Explore and the Assistant
Section titled “Explore and the Assistant”Review exploration proposalsAccept, edit or reject the changes the exploratory agent proposes, then apply them.
Create tests with the AssistantDescribe a test in a chat, confirm it, and the Assistant creates it.
Reference and help
Section titled “Reference and help”Troubleshoot failed testsWork out why a test failed and what to change.
Limits and defaultsTime limits, credential sessions, schedules, list sizes and Assistant limits.
GlossaryThe terms used across Testmode and these docs.
FAQAnswers to common questions about using Testmode.
testmodeBetter software quality. No manual testing. Your team knows the software. Testmode does the testing.