SQL Tester
Test stored procedures, functions, views and plain SQL against your own databases. Every run is kept, runs roll back by default, and Production is read-only.
- Run your first SQL statement - Create a project, add a database and run a statement in the Scratchpad.
- Try SQL without saving a test - Run a query in the Scratchpad, or on a practice copy of the sample database that is yours alone, and save nothing until you choose to.
- Add an environment - Connect a project to a database: provider, encrypted connection string, tier and test.
- Read a run's result - What the verdict, result sets, rows, parameters and errors on a result mean.
- Save a run as a test and run it again - Turn a Scratchpad run into a test, then run one test, a group or all of them from the Tests board.
- Set up a test in the editor - Every field of the test editor, including setup SQL and extraction.
- Decide pass or fail with checks - The check types, operators and result paths a test can check.
- See what changed since a test last passed - How SQL Tester compares runs and flags drift without any check.
- Reuse values with variables and chaining - Use {{name}} variables, keep secrets masked, and pass a value from one test to the next.
- Find untested objects with the catalog - Sync an environment, see coverage per object and generate boundary tests and data checks.
- Read the History tab - What the tiles and cards on the History tab count.
- Safety tiers and transaction modes - What each tier allows, how transaction modes work and what is never allowed.
- What a run keeps, and for how long - What every run stores, how long it stays, and the audit trail.
- Load test a test - Run one test many times at once and read the latency distribution.