Web and Databases for Quality Assurance (QA)s
Web and databases is the technical background a tester needs to examine an application from the inside: HTML, CSS and the DOM for locating elements, HTTP and REST for understanding requests, browser dev tools for debugging, and SQL for checking that the data stored is correct.
Stage: Technical Foundations · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Web and Databases
- Read the DOM tree and write a stable CSS selector for an element
- Inspect a request and response in the browser Network tab
- Explain common HTTP methods and status code families
- Reproduce a UI action as a REST call
- Write SELECT queries with joins to validate saved records
- Spot data errors using COUNT, GROUP BY and NULL checks
Web and Databases interview questions
What is the difference between a 401 and a 403 status code?
401 means the request lacks valid authentication, so the server does not know who you are. 403 means the server knows who you are but you are not permitted to access that resource. Testing both confirms login and authorisation rules separately.
How do you verify with SQL that a UI form saved correct data?
Submit known test data through the UI, then query the relevant table by a unique value and compare each column with what you entered. Also check related tables for foreign keys, timestamps and that no duplicate rows were created.
Where Web and Databases fits in the Quality Assurance (QA) roadmap
Web and Databases belongs to the Technical Foundations stage (beginner level), which takes about 5 hours. The skills automation needs.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap