DevTools for Testers

DevTools are the developer tools built into the browser. They show what the interface hides: which requests the page sent to the server, what the server answered, and what the site stored in the browser.

What you gain: you can tell whether a defect is on the client or the server, attach the exact request and response to a bug report, reproduce scenarios such as “first visit to the site” on your own, and find out what happened without waiting for a developer.

What DevTools are and how to open them

Open DevTools with F12 or Ctrl+Shift+I (Cmd+Option+I on Mac). Testers most often need two tabs: Network with the page’s requests and Application with the browser’s storage. Unlike Postman, where you send a request yourself, DevTools shows the requests the page sent on its own when the user pressed a button or opened a section.

The Network tab: requests and responses

Network is a table of all the page’s requests. Clicking a row opens Headers (address, method, status code), Payload (request body), and Response (the server’s answer). The Fetch/XHR filter leaves only API requests, without images and styles. This is how you check exactly what went to the server and what it returned.

Example. The “Save” button does nothing. If Network shows no request, the problem is on the client. If the request went out and returned 500, the error is on the server. If it returned 200 with the right data but the screen did not update, the client is at fault again.

The Application tab: cookies and storage

Application shows what the site stores in the browser: Cookies, Local Storage, and Session Storage. Records can be viewed, edited, and deleted. A cookie is a small “name=value” record that the browser sends to the server in the Cookie header with every request on its own. For example, the site remembers the user’s choice in the GDPR banner in a cookie such as cookie_consent=all.

Example. To test the “first visit to the site” scenario you do not need a new browser: delete cookie_consent in the Application tab and reload the page, and the consent banner appears again.

DevTools in a bug report

A good bug report about a data problem contains not only steps and a screenshot but also what DevTools showed: the request address and method, the status code, and the request and response bodies. The developer does not have to reproduce the defect to know where to look, and you can decide yourself whom to assign the bug to: the frontend or the backend.

Test yourself in the bug reports quiz