Defect types require the Pro plan or above. On the Free plan, labels already on your test runs stay visible, and new labels cannot be added. See Pricing.
Quick Reference
Create defect types
A new project has no defect types. An owner or administrator adds them from the Defect Types sheet, which opens from any test run:- Open a defect type picker on a failed or flaky test case and click Manage defect types at the bottom.
- Or, on the Summary tab, click the settings icon on the Defect types card. The card appears once the test run has at least 1 label.
Click Add Defect Type and fill in the form:
A project holds up to 20 active defect types. The sheet header shows the count, for example 5 of 20 active. Archived defect types do not count toward the limit.
Create from the picker. Owners and administrators can also type a new name into the picker search and click Create "<name>". The defect type is created with the next free color and applied in the same step. Add a description later from the sheet.
Label a test case
Labels go on failed and flaky test cases in a finished test run. The control appears once TestDino has finished processing the run.
Click the control, search, and pick a defect type. The chip updates right away and shows the label everywhere that test case appears in the run.
To change a label, open the chip and pick another defect type. To remove it, open the chip and click Clear defect type.
Label an error group
On the Errors tab, each error group has a Label group button. Picking a defect type labels every failed and flaky test case in the group, including test cases that already had a different defect type.
A toast confirms the result, for example Labelled 12 tests as Product bug., with an Undo action that puts every test case back to the label it had before.
The group button shows the group’s current state:
When a large group shows only
Showing the first N of M tests with this error, a group label goes only on test cases that have no label yet. Test cases that already have a defect type keep it.
The Label group button is hidden while a search or tag filter is active on the Errors tab. Clear the filter to label the whole group.
Add a reason
A reason is a short note on 1 test case that explains why its label applies, for exampleCheckout API returns 500 since the deploy on Monday.
- Open the test case’s chip and click Add reason.
- Enter up to 2,000 characters and click Save Reason.
Filter a test run by defect type
Once a test run has at least 1 label, the Summary tab shows a Defect types card above Detailed Analysis:- A bar that splits the run’s failed and flaky test cases by defect type, with Not triaged last.
- A progress line, such as
75% triaged · 3 left, orAll 12 tests triagedwhen nothing is left. - A legend chip per defect type. Click a chip to filter the table to that defect type.
The Defect type filter in the Summary tab’s filter menu does the same. It lists each defect type used in the run with its count, for example Product bug (4), plus Not triaged (3) for failed and flaky test cases with no label yet. Use Not triaged as your triage queue.
Manage defect types
Owners and administrators manage defect types from the Defect Types sheet. Each row’s actions menu offers:- Edit renames it, changes its color, or updates its description. A rename updates the label on every test run, including past ones.
- Archive removes it from the pickers so nobody applies it again. Labels already on test runs stay visible. Archived defect types are listed under Archived in the sheet and free a slot toward the limit.
- Restore makes an archived defect type available in the pickers again.
- Delete removes a defect type that was never used. It cannot be undone. A defect type that has been used can only be archived.
Roles and permissions
Members see No defect types yet in the picker until an owner or administrator adds some. Full role details are in Users & Roles.
Troubleshooting
This run is still being processed. Try again in a moment.
This run is still being processed. Try again in a moment.
The test run finished moments ago and TestDino is still processing its results. Wait a few seconds and apply the label again.
This project has reached its defect type limit. Archive one to add another.
This project has reached its defect type limit. Archive one to add another.
The project already has 20 active defect types. Archive one you no longer use from the Defect Types sheet, then add the new one.
A defect type with this name already exists.
A defect type with this name already exists.
Another active defect type in the project uses that name. Pick a different name, or rename or archive the existing one first.
This defect type is used on runs, so it can only be archived.
This defect type is used on runs, so it can only be archived.
A defect type that has labelled any test case cannot be deleted. Archive it instead: it leaves the pickers and its labels stay on past test runs.
Every test in this group already has a type.
Every test in this group already has a type.
Every test case in the error group already carries the defect type you picked, so nothing changed.
This error group is too large to label at once.
This error group is too large to label at once.
The group holds more test cases than a single group label can change. Label test cases from their rows, or narrow the group with search first.
You need at least member access to perform this action
You need at least member access to perform this action
Your role is Viewer or Billing Manager, which can see labels but not set them. Ask an owner or administrator to change your role.
Defect types are available on Pro
Defect types are available on Pro
The organization is on the Free plan. Labels already on your test runs stay visible. Click Upgrade to Pro to add and apply defect types.
Related
Run Summary
Failed, flaky, and skipped test cases in a test run.
Errors tab
A test run’s failures grouped by error message.
Error grouping
How TestDino groups failures by root cause.
Users & Roles
What each role can do in a project.