Key takeaways
- Press F12 (or Cmd+Option+I on a Mac) in Chrome, Edge or Firefox to open DevTools. It's free, already installed, and one of a web tester's most useful tools.
- The Network panel shows every request and response: status codes, data sent and received, timings. The Console shows JavaScript errors. Together they explain most "nothing happens" bugs.
- Use device mode for quick mobile checks, Application for cookies and storage, and Elements to inspect what's on screen. Attach what you find to your bug reports.
Why DevTools matter
When a user clicks a button and nothing happens, there are many possible causes: a JavaScript error, a request that failed, a request that succeeded with the wrong data, or no request at all.
From the screen, all four look the same. DevTools tells you which one it is. That's the difference between a vague bug report and one a developer can fix immediately.
This article uses Chrome. Edge is nearly identical, and Firefox and Safari have the same panels with slightly different names.
1. Elements: what's on the page
The Elements panel shows the page's HTML and CSS. Right-click anything on the page and choose Inspect to jump to it.
Use it to:
- check text that's cut off, hidden or overlapping, and see which style causes it;
- find an element's attributes, such as an
id, adisabledflag, or a missingalttext on an image (accessibility); - temporarily edit text to test layout, for example pasting a 60-character name to see if the design breaks.
2. Console: errors and messages
The Console shows messages from the page's JavaScript, and above all errors in red.
Use it to:
- check for errors when something "does nothing": a red
TypeError: Cannot read properties of undefinedright after your click explains a lot; - copy the full error text into your bug report.
Tip: keep the Console open while you test. Many bugs leave a red line before anyone sees a visible problem.
3. Network: every request and response
This is the most valuable panel for testers. It lists every request the page makes.
- Open the Network tab before you do the action (or reload the page).
- Tick Preserve log so the list isn't cleared when the page navigates.
- Filter by Fetch/XHR to see only the data requests the app makes, without images and styles.
- Do the action, such as clicking "Save".
- Click the new request and look at Headers (URL, method, status code), Payload (what was sent) and Response (what came back).
What to look for:
- a red request: status 4xx or 5xx;
- a request that never appears, so the click didn't trigger anything;
- a 200 response with the wrong data, such as a total of 0 or a missing field;
- a request that takes seconds (see the Time column).
The Network panel also lets you throttle the connection ("Slow 4G", "Offline") to see how the app behaves on a poor connection, a great source of bugs.
To share evidence, right-click a request: Copy → Copy as cURL lets a developer replay it exactly. You can also save everything with Save all as HAR.
4. Application: cookies and storage
The Application panel (called Storage in Firefox) shows what the site keeps in your browser: cookies, local storage and session storage.
Use it to:
- check that logout really deletes the session cookie;
- delete a cookie to simulate an expired session, then see what the app does;
- check that sensitive data, like a full card number, is not stored in local storage, where any script on the page can read it.
See how the web works for what cookies and sessions do.
5. Device mode: quick mobile checks
Click the phone/tablet icon (or press Ctrl+Shift+M / Cmd+Shift+M) to see the page at a phone's screen size, with touch events.
Use it to check layouts on different widths quickly. But remember: it's a simulation of the screen size, not a real phone. It won't show bugs specific to Safari on iPhone, or a real device's performance. Final checks belong on real devices; see mobile app testing.
A tester reported: "Profile page: clicking Save does nothing." The developer couldn't reproduce it, and the bug went back and forth for two days.
Then the tester opened DevTools. The Network tab showed that Save sent PATCH /api/profile and got 400 Bad Request. The response said: "phone": "invalid format". The tester's phone number had a space in it, 0722 123 456, which the server rejected. The front end received the error but never displayed it.
The updated report had the request, the response and the exact data. It was fixed the same afternoon: the front end now shows the validation message, and the server accepts spaces.
Lesson: "nothing happens" is where you look in DevTools. Usually something did happen; it just wasn't shown on screen.
A DevTools checklist for every bug report
- Any red errors in the Console? Copy the text.
- What did the request look like? Method, URL, payload.
- What was the response? Status code and body.
- How long did it take, if speed is the issue?
- Which browser and version? (
chrome://versionshows it.)
Do
"Save sends PATCH /api/profile and gets 400 with {"phone":"invalid format"} when the phone contains spaces. No message is shown to the user. Screenshot of Network tab and response attached."
Don't
"Save button doesn't work." It may be accurate, but it leaves the developer to repeat your entire investigation.
Check yourself
You click 'Place order'. The spinner turns forever. In the Network tab, the POST /api/orders request shows '(pending)' for over a minute, then fails. The Console is clean. What does this suggest, and what would you put in the bug report?
Show answer
The front end did its job: it sent the request and is waiting. The problem is on the server side or in between: the server is too slow, stuck, or a dependency like the payment provider isn't responding. Report the request (URL, method, payload), how long it stayed pending, the final error or status, the time it happened (so developers can find it in server logs), and that the user gets no timeout message, which is a second, front-end bug.
