Meet DevTools
What DevTools are, how to open them, how they differ from Postman and why a tester needs the Network and Application tabs.
About the task
What DevTools are, how to open them, how they differ from Postman and why a tester needs the Network and Application tabs.
Application under test
Hi! You already know Postman. Now let’s look at requests from the other side: from inside the browser, with DevTools.
What is DevTools?
DevTools are developer tools built into the browser. Open them with F12, Ctrl+Shift+I (Cmd+Option+I on Mac), or right-click the page → “Inspect”.
They work on any site and there’s nothing to install.
How is it different from Postman?
In Postman you send a request yourself. In DevTools you see the requests the page sent on its own when the user pressed a button or opened a section.
That way a tester checks exactly what went to the server and what it answered, without inventing a request by hand.
Which tabs are there?
There are many tabs. For now we need two: Network and Application. We’ll cover the rest later.
Why does a tester need it?
To find out whether a request was sent at all. To see the method, address, status and body. To tell a client bug from a server bug. And to attach all of it to a bug report so the developer doesn’t have to guess.
Where do cookies and Local Storage live?
Great! Next in this block we’ll open Network and send requests with a mini interface, and then look at Application.
Quick reference
DevTools
The developer tools built into the browser. Open them with F12 or Ctrl+Shift+I (Cmd+Option+I on Mac).
Network
A table of the page’s requests. Clicking a row opens Headers (address, method, status), Payload (request body) and Response. The Fetch/XHR filter leaves only API requests.
Application
Browser storage: Cookies, Local Storage, Session Storage. Records can be viewed, edited and deleted.
Cookie
The browser sends cookies to the server with every request.