Skip to main content
What you’ll learn
  • What evidence TestDino collects for each test execution
  • How to use traces, screenshots, and videos to diagnose failures
  • How AI classification and error grouping speed up triage
TestDino collects evidence from each test execution: screenshots, videos, traces, console logs, and error details. Understand failures without re-running tests locally.

​
Evidence Types

EvidenceWhat it showsWhen to useGuide
ScreenshotsVisual state at failure pointUI layout issues, missing elementsVisual Evidence
VideoFull test execution recordingTiming issues, unexpected interactionsVisual Evidence
TraceStep-by-step execution with network and DOMComplex failures, race conditionsTrace Viewer
ConsoleBrowser console outputJavaScript errors, API failures-
Error detailsError message and stack traceAssertion failures, exceptionsError Grouping

​
Where to Find Evidence

Open a test run and click on any failed test. The test case details page shows:
  1. KPI tiles: Status, runtime, retry attempts
  2. Evidence tabs: One tab per attempt (Run, Retry 1, Retry 2)
Test case KPI tiles showing status, runtime, and retry count Each evidence tab contains:
  • Error details with stack trace
  • Test steps with timing
  • Screenshots
  • Console output
  • Video player
  • Trace viewer link
  • Visual comparison (for screenshot tests)
Evidence panel showing error details, screenshots, console, and video tabs

​
Debugging Workflow

1

Check the error message

Start with the error details. The message often points to the issue: assertion mismatch, element not found, or timeout.
2

Check the error group

Look at the error category (assertion failure, timeout, element not found, etc.) to determine whether to fix code, update selectors, or stabilize the test.
3

Look at screenshots

Screenshots show the UI state at failure. Compare with expected behavior.
4

Watch the video

Videos reveal timing issues and unexpected interactions that screenshots miss.
5

Open the trace

Traces provide the most detail: every action, network request, and DOM change. Use traces for complex failures.
6

Check console logs

Console output shows JavaScript errors, failed API calls, and application logs.

​
AI Categories

CategoryWhat it meansAction
Actual BugRepeatable product defectFix application code
UI ChangeInterface changed, test no longer matchesUpdate selectors or assertions
Unstable TestIntermittent failure from timing or stateStabilize the test
MiscellaneousEnvironment or configuration problemFix infrastructure or CI
AI Insights showing category, confidence score, and suggested fixes
TipEach classification includes a confidence score. Use the feedback form to correct misclassifications.

​
Next Steps

Trace Viewer

Step-by-step execution analysis

Visual Evidence

Screenshots and videos

Error Grouping

Find patterns across failures

Test Cases

Full test case documentation