Approvals
TestFlair AI never changes your data silently. When it wants to create, update or delete something, it stops and shows you an approval card describing exactly what it proposes to do. Nothing is written until you decide.
TestFlair AI is a Beta feature and may not be visible on every account. Contact your workspace admin or [email protected] if you'd like access.
The Three Decisions
| Decision | What happens |
|---|---|
| Accept | The change is applied exactly as shown |
| Edit | You correct the details first, then the corrected version is applied |
| Reject | Nothing is applied. You can say why, and the assistant takes that into account |
Rejecting is not a dead end — an explanation goes back to the assistant, so "reject: the acceptance criteria should cover the logged-out case too" usually produces a better proposal rather than the same one again.
Edit replaces the whole proposal, not just the field you touched. The card shows every value; what you submit is what gets applied.
Deletions
Deletions offer Accept or Reject only — there is no Edit.
That is deliberate rather than an oversight. There are no arguments worth correcting on a deletion, and offering Edit would imply the deletion could be narrowed, which it cannot. It either happens or it doesn't.
What Requires Approval
Anything that changes platform state:
| Work item | Actions that ask first |
|---|---|
| Test case | Create, update, delete |
| User story | Create, update, delete |
| Test script | Update, delete |
| Bug | Create, update, delete |
Reading costs you nothing and asks nothing — listing test cases, looking up a user story or checking a project's statistics all happen without interruption.
If the assistant did something you did not expect and were not asked about, it was a read. Anything that wrote to your project would have shown you a card first.
Reviewing a Proposal Well
The card exists so you can catch a wrong proposal before it becomes a wrong record. Worth checking:
- The right item. On an update or delete, confirm it names the item you meant.
- The right project. Mention the project with
@if there is any doubt. - Completeness. On a create, thin acceptance criteria or missing steps are easier to fix in the card than after the fact.
Troubleshooting
I approved something by mistake
- The change is applied like any other edit. Fix it in the web app, or ask the assistant to change it back — which will show you a fresh approval card.
The Edit button isn't there
- It is a deletion. Those are accept-or-reject only.
I rejected and got the same proposal again
- Say why when you reject. A bare rejection tells the assistant nothing about what was wrong.
Next Steps
- TestFlair AI — Chat, mentions and slash commands
- Test Cases — What most approvals are about
- Bugs — Bug records the assistant can create