“Has this been tested?”
A finished card does not show which scenarios were checked.
TestMaster Flow
Built for lean teams. With room to grow.
Know what was tested. See what needs attention.
If tests live in spreadsheets or your team’s memory, start organizing project quality. Bring together what needs to work, the tests performed and the problems found, so your team can decide what to do next with more clarity.
30 free days, no card. One account for TestMaster, PlanMaster and BugMaster.
AN EXAMPLE OF YOUR NEXT WORKFLOW
From idea to evidence.
- 1
Define what needs to work
Organized requirements and acceptance criteria.
- 2
Turn criteria into tests
AI-assisted drafts, reviewed by your team.
- 3
Run tests and record results
Steps, environment and evidence in context.
- 4
Track what needs fixing
Bugs linked to tests, with owners on the board.
A path to follow, even without a dedicated QA team.
- Requirementwith acceptance criteria
- Test caseDefault or BDD
- Runwho, when, where
- Bugon the bug board, with its origin
A finished task does not tell you what was tested.
If your team uses spreadsheets, cards and conversations to stay organized, these situations may feel familiar.
“What failed in the last run?”
Results and evidence are scattered across spreadsheets and conversations.
“Can we release?”
Without linked requirements and results, the team has to reconstruct the testing context.
Three questions to understand a delivery.
PlanMaster organizes work. TestMaster shows coverage and recorded results. Together, they help your team decide where to act.
How is the work progressing?
Activities, owners, priorities and progress together in PlanMaster.
Find pending work and see who owns the next step.
What has been validated?
Cases linked to acceptance criteria, with results recorded in test runs.
See what passed, what failed and what has not been executed.
What needs attention?
Uncovered criteria and outstanding bugs guide the next quality discussion.
Use the records to assess a delivery and decide what to check or fix.
Coverage means an active case is linked to a criterion. Passing depends on the execution result. Both help you assess project quality.
How it works
Four steps, and the trail survives all of them.
- 01
Write the requirement and its acceptance criteria
Each criterion becomes a folder in the suite with one click. The link between criterion and case survives an edit to the text, so fixing a typo does not undo your coverage.
The requirements screen: every acceptance criterion shows how many cases cover it. - 02
Build the cases, Default or BDD
In BDD each step carries its own Given/When/Then, preconditions become the Background, and the expected result only appears on steps that assert something. Converting between the two styles loses no text.
A case written in BDD: the keyword lives on the step itself. - 03
Run it
From a plan or ad hoc. The runner is driven from the keyboard (P, F, B, S, N) and records who ran it, when, and against which environment.
The runner: one case at a time, with a keyboard shortcut for each result. - 04
Open the bug from the step that failed
Title, steps to reproduce, environment and version arrive filled in from the run. The bug lands on the Kanban carrying its origin with it.
The bug board, with columns configured per project.
In motion
Three things a still image cannot show.
Dragging saves immediatelyThe card changes column and the position sticks. No save button, and no waiting for a page to reload. The run is driven from the keyboardP for passed, F for failed, B for blocked, S for skipped. Your hand never leaves the keyboard for a whole batch. From the failed step to the bugOne click on the failed result opens the bug with title, steps, environment and version already filled in.
What is already built
The screen that answers "was there a test for this?"
Acceptance criterion by acceptance criterion: which ones have an active case, how many are left as gaps, and how much of the total is covered. A requirement only counts as fully covered when all of its criteria are, and cases in draft or obsolete do not count.
The same screen splits coverage by kind of test: manual, unit, integration, API, E2E and exploratory. A criterion defended only by a manual test is a different risk from one defended by automated E2E, and here that difference shows instead of disappearing into a single number.
Explore more features and screens
AI on your own key, inside the flow
Draft requirements, cases and bugs with a screenshot or log attached. Choose your personal Gemini or OpenAI connection; the provider bills usage to your account. Without a key, build the prompt, use an external AI and import the answer back.
Your data leaves whole, whenever you want
A zip with a faithful project.json, one CSV per entity and the attachments alongside, plus a README explaining the layout. Tried it and did not like it? Take everything. The way out is part of the product.
Run report
Two separate charts, because progress and pass rate do not share a denominator. A run still open is marked as open.
Search with combined filters
Severity, priority, assignee, environment, version, tag, column and state, each accepting several values at once. The filters live in the URL, so the link reproduces the search.
A report ready to become a PDF
It opens formatted, with the filters spelled out. And CSV and JSON carry exactly what the screen has filtered.
A bug board with your columns
Every project defines its own columns, with colour and order. Dragging saves immediately.
Nested suites
Sub-suites with drag and drop. Selecting a suite also shows the cases of its children.
Bug search with two severities selected at once, and the filter carried in the URL. 
A run report: two charts, because progress and pass rate do not share a denominator.
AI and MCP to reduce manual work
More time to investigate. Less time entering records.
Ask your assistant to turn criteria into cases, organize a plan and record the results your team provides. When a test fails, create a bug linked to the result and requirement to help developers investigate.
Product owners
Requirements ready for a team discussion
Connected requirements, criteria and documentation to guide refinement and test preparation.
Less duplicate entry between product definition and planning.
Developers
Planning in the context of implementation
Activities linked to their requirement, epic and sprint, so the team can find the purpose behind the work.
Fewer screen changes to record and track the work ahead.
QA engineers
From test preparation to a traceable failure
Connected cases, plan, results and bug. The failure keeps its reference to the test and requirement.
Less manual work assembling context to investigate and fix failures.
An API for your team’s existing workflows
The API helps bring information from other systems and keep project data up to date, reducing duplicate entry across tools.
Your next step: work and quality in one solution.
For teams moving beyond spreadsheets and cards, TestMaster + PlanMaster connects the work to be done with delivery validation. See the benefit compared with each alternative.
| Tool | What you get | Why choose TestMaster + PlanMaster |
|---|---|---|
| Spreadsheets | Flexible data organization. | Structured tests and links, without building the process in cells. |
| Trello | Boards to organize tasks. | Also see what was tested and what failed. |
| Jira | Development planning. | Test management is already part of the joint offering. |
| Jira + Xray | Planning, testing and traceability. | One joint offering, without depending on Jira and an Xray license. |
| TestRail | Test management and reports. | Development planning included with PlanMaster. |
| TestLink | Open-source test cases, plans and runs. | Bugs, requirements and planning in the same project, without integrating another tool. |
| Bugzilla | Open-source bug tracking. | Cases, runs and coverage linked to the bug, not just the defect record. |
| TestMaster + PlanMaster | Connected requirements, work, tests and bugs. | Follow activities through to test results in the same project. |
Spreadsheets
- What you get
- Flexible data organization.
- Why choose TestMaster + PlanMaster
- Structured tests and links, without building the process in cells.
Trello
- What you get
- Boards to organize tasks.
- Why choose TestMaster + PlanMaster
- Also see what was tested and what failed.
Jira
- What you get
- Development planning.
- Why choose TestMaster + PlanMaster
- Test management is already part of the joint offering.
Jira + Xray
- What you get
- Planning, testing and traceability.
- Why choose TestMaster + PlanMaster
- One joint offering, without depending on Jira and an Xray license.
TestRail
- What you get
- Test management and reports.
- Why choose TestMaster + PlanMaster
- Development planning included with PlanMaster.
TestLink
- What you get
- Open-source test cases, plans and runs.
- Why choose TestMaster + PlanMaster
- Bugs, requirements and planning in the same project, without integrating another tool.
Bugzilla
- What you get
- Open-source bug tracking.
- Why choose TestMaster + PlanMaster
- Cases, runs and coverage linked to the bug, not just the defect record.
TestMaster + PlanMaster
- What you get
- Connected requirements, work, tests and bugs.
- Why choose TestMaster + PlanMaster
- Follow activities through to test results in the same project.
Start with TestMaster. Add PlanMaster to your workflow when you want to connect development planning too.
Comparison notes and sources
Workflow comparison reviewed October 11, 2026. Spreadsheets, Trello and Jira are considered without added test management apps; Jira + Xray includes that app. Features and terms vary by plan, edition and integrations. Xray and TestRail also provide coverage and traceability. The Jira + Xray column refers to Xray Test Management, an app for Jira. TestLink is considered in its open-source edition, without integrations; Bugzilla is a bug tracker and does not offer test management. Visibility in our solution depends on the records and links maintained by your team.
Official sources: features and licensing.TrelloTrello plansTrello MCPJira and test managementXray featuresXray licensingTestRail features and plansTestRail and JiraTestLink documentationBugzilla documentation
Start by organizing one feature in your project.
Choose something your team knows, such as login or registration. You can start without a dedicated QA specialist and grow your process gradually.
- 01
Describe the expectation
Write the rule and how to tell whether it works.
- 02
Organize the work
Create activities, set priorities and assign owners.
- 03
Prepare a few tests
Record the steps and expected results.
- 04
Record what happened
Execute with your tools and record results and failures.
- 05
Review and improve
Check pending work and agree on next steps.
Add epics, sprints and advanced features as your team needs them. Your first step can be one requirement, one activity and one test.
Build on what is already in your spreadsheet or board.
Start with a small set of information so you can check the organization before bringing more data across.
- 01
Select
Pick one feature and collect its existing notes, tasks and tests.
- 02
Organize
Identify requirements, activities, test cases and bugs. Review titles, owners and relationships.
- 03
Create and check
Use the interface or provide the data to your MCP-connected assistant. Check the records and links before expanding.
For larger volumes, the API supports building integrations from available data. Formats, fields and links need mapping; this workflow is not an automatic importer for Trello or arbitrary spreadsheets.
Frequently asked
- Is there a Wiki to help with QA questions?
- Yes. The Software Quality Wiki provides articles, search, a glossary, templates and exercises for people getting started or looking up a question. Contextual help connects concepts such as acceptance criteria, test cases and bug reports to the work you are doing. Article content is in Portuguese.
- Do I need QA expertise to get started?
- Start by describing what the product should do through requirements and acceptance criteria. AI helps draft requirements and tests; your team reviews the content and decides what to validate. The workflow gives you structure, and questions can be sent through the support channel.
- What does it cost, and how does support work?
- Access is reviewed individually. Price ranges in the form are research, not a plan offer. Send questions or problems through the support page and receive a reply by email.
- Do I have to install anything?
- No. It runs in the browser.
- How do I get access?
- Create your account in seconds, no card needed. The same account opens TestMaster, PlanMaster and BugMaster and starts with 30 free days. It starts without a project of its own; you can explore read-only showcases and create your first project when ready.
- Is it any use for one person?
- It is. Project, suite, case and run work the same with one person or ten. What changes is how many people you invite.
- Can I get my data out?
- At any time. CSV and JSON on bugs and runs carry what the screen has filtered, and the full export downloads a zip of the whole project, with project.json, one CSV per entity and the attachments. You can export an entire organisation too.
- Can I control who sees what?
- Yes. The organization defines roles and their permissions, enables roles in projects and assigns them to participants. Access follows each person’s responsibilities within the organization’s permission limits.
- Where does the data live?
- In TestMaster Flow's own database. Access requires login, and what each person can see and do depends on organization permissions and their assigned project role.
- Does it work with BDD?
- Yes, with Given/When/Then on the step itself. And converting a case already written in one style to the other loses no text.
- Do I need an AI key?
- To generate inside the app, save your Gemini or OpenAI key under My account → AI connections. You can keep both and select which to use. The provider bills usage to your account. Without a key, you can still build the prompt, use an external AI and paste the answer back.
- If I delete a case, do I lose the history?
- No. Past runs stay identical, with the same totals and the same rows, and the case appears in them marked as archived.
- Is the product in English?
- Yes. The interface has English and Portuguese, and each person picks theirs. The screenshots on this page are the English one.
- Who owns the AI account and pays for token usage?
- You use your own AI account. The customer is responsible for subscriptions, limits and token usage costs under the selected provider or assistant. With MCP, your AI provider account and credentials are configured in your assistant; TestMaster receives requests to read and change authorized records.
- Does TestMaster store anything related to AI?
- For in-app AI, the provider key is stored encrypted so it can be used. Saved requirements, documents, tests and other content remain in the project, including content prepared with AI. For an external assistant connected through MCP, conversations and data handling follow that assistant’s settings and the policies of the provider selected by the customer.
- Can I use TestMaster without PlanMaster?
- Yes. You can manage requirements, tests, runs and bugs in TestMaster without adopting PlanMaster in your daily workflow. We recommend using both to connect development activities to the same requirements and follow planning and quality together. The joint offering does not require your team to use both products.
Know what was validated before deciding to release.
Choose one important feature. Organize its tests and results so your team can see what passed, what failed and what remains to be checked.
Simple plans, paid by card or Pix
Start with 30 free days on the Team plan, no card needed. One account opens TestMaster, PlanMaster and BugMaster. Then pick a plan and pay monthly by card or Pix.
Essential
To start with a small team.
R$ 79/month
- Up to 3 users
- Up to 2 projects
- TestMaster + PlanMaster, with BugMaster access
- Most popular
Team
The whole team, with testing and planning together.
R$ 150/month
- Up to 10 users
- Up to 5 projects
- TestMaster + PlanMaster, with BugMaster access
Business
Several teams and products in one account.
R$ 390/month
- Up to 30 users
- Up to 20 projects
- TestMaster + PlanMaster, with BugMaster access
Monthly payment by card or Pix. No lock-in. Every delivered BugMaster session adds 1 month of TestMaster and PlanMaster. Discover BugMaster