Run SQL on a sample QA database
A real SQLite database runs inside your browser with customers, orders, products and defects already loaded. Write a query, press Run, see the rows – nothing is sent to any server.
SQL editor
Loading the database…Sample database
Four tables with realistic data, the same shape you meet on a real project. INSERT, UPDATE and DELETE work too – press Reset database to put the sample data back.
customers
id · name · email · city · created_at
orders
id · customer_id · product_id · amount · status · order_date
products
id · name · category · price · stock
defects
id · title · module · severity · priority · status · raised_by
Try these – the queries interviewers ask
Click any example to load it into the editor, then change it and run it again – that is how the query sticks in your memory.
What a tester uses SQL for
- Verify the database after a UI or API action – right values, right status, audit columns written
- Prove a duplicate-record defect with one GROUP BY … HAVING query
- Prepare and clean test data before a run
- Check a report total against the raw rows behind it
- Answer the SQL round, which comes up in almost every QA interview