Read a run's result
What the verdict, result sets, rows, parameters and errors on a result mean.
In short
A result shows whether the run passed, how long it took, the rows and result sets it returned, output parameters, server messages, and whether the transaction rolled back. A failed run names what went wrong.
Before you start
- Who: anyone who can open the project reads results (View).
- Plan: every run counts toward your plan, and one person can start at most 30 runs a minute.
- First: run a test or a Scratchpad statement.
Read a result
- Run a test or a "Scratchpad" statement.
- Read the verdict, "Passed" or "Failed", and the time in milliseconds.
- Read the result sets, rows, rows affected, return value and output parameters.
- Click a cell in a result grid to add a Cell value check for exactly that cell.
A result grid has "Download rows (CSV)", which saves the rows on screen as a CSV file. A practice run from "Try it (not saved)" shows the same grid; see /help/sql-tester/try-it-not-saved.
If something goes wrong
A failed run names its cause: syntax error, permission denied, timed out, deadlock, constraint violation, connection failed, object not found, invalid input or refused by policy.
Related
- /help/sql-tester/assertions
- /help/sql-tester/what-changed
- /help/sql-tester/saving-cases