Skip to main content
Defect types are labels your team defines for why a test case failed, such as Product bug, Automation bug, or Environment issue. Each project has its own set. Defect types are assigned by your team. Failure classification is the category TestDino’s AI assigns to every failure. A test case can carry both.
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. To open it, open a defect type picker on a failed or flaky test case in any test run and click Manage defect types at the bottom. Defect Types sheet listing active defect types with color chips, usage counts, and descriptions, with the Add Defect Type button and the active count in the header Click Add Defect Type, enter a name (up to 40 characters, unique in the project), pick a color, and optionally add a description (up to 200 characters). Click Add Defect Type in the form to save it. Add Defect Type form with the Name field, the color swatches with a live chip preview, and the optional Description field A project holds up to 20 active defect types. Archived defect types do not count toward the limit. To create and apply a defect type in 1 step, type a new name into the picker search and click Create "<name>".

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 the failed and flaky test cases in the group: Errors tab with an expanded error group and its Label group picker open, listing the project's defect types A toast confirms the result, for example Labelled 12 tests as Product bug. Click Undo in the toast to put every changed test case back to its previous label and reason. The group button shows the group’s current state: 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. 2 group actions ask for confirmation first: Each dialog states how many test cases change and whether any reasons are removed. After a clear, the toast Cleared defect type from N tests. offers Undo.

Add a reason

A reason is a short note on 1 test case that explains why its label applies, for example Checkout API returns 500 since the deploy on Monday.
  1. Open the test case’s chip and click Add reason.
  2. Enter up to 2,000 characters and click Save Reason.
The chip shows a note icon, and the reason appears in the chip’s tooltip wherever the label shows. Use Edit reason to change it.
A reason belongs to its defect type. Changing a test case’s defect type, by hand or through Label group, replaces its reason. Undo on a group label restores it.
When you pick a new defect type for a test case that has a reason, the Change Defect Type dialog opens with Moving to <type>. Add a reason for it, or leave this empty. and shows the Previous reason. Enter a new reason or leave it empty, then click Change Type.

Filter a test run by defect type

Open the Summary tab’s filter menu and use the Defect type section to select 1 or more defect types. The section appears only when the run has failed or flaky test cases. 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. The selection is part of the page URL, so a filtered Summary tab can be shared as a link.

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

Owners and administrators create and manage defect types. Members label test cases and error groups and add reasons. Viewers and Billing Managers see labels but cannot change them. Full role details are in Users & Roles.

Troubleshooting

Labels go only on failed and flaky test cases in a finished test run. The control is hidden while the run is in progress, on a run with no failed or flaky test cases, and for a few seconds after the run finishes. On the Free plan, it is hidden on test cases that have no label. If you see This run is still being processed. Try again in a moment., wait a few seconds and apply the label again.
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 that has labelled any test case cannot be deleted. Archive it instead: it leaves the pickers and its labels stay on past test runs.
The group has more than 5,000 test cases, more than a single group label can change. Label the test cases from their rows instead.
Your role is Viewer or Billing Manager, which can see labels but not set them. Ask an owner or administrator to change your role.
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.

Run Summary

Failed, flaky, and skipped test cases in a test run.

Errors tab

A test run’s failures grouped by their cause.

Error grouping

How TestDino groups failures by root cause.

Users & Roles

What each role can do in a project.
Last modified on October 13, 2026