Check out out my article, “10 powerful tests with Chrome DevTools,” on the MoT site to gain a clear understanding of how to use Chrome DevTools for effective testing.
Whether you’re testing at the UI level or the functional level, Chrome DevTools can help both developers and testers troubleshoot issues. This article is packed with information on how to use Chrome DevTools for different purposes.
What You’ll Learn:
How to access and navigate Chrome DevTools.
Inspecting and debugging HTML and CSS issues.
Steps to debug JavaScript errors and track down bugs in the code.
Using the cCnsole to run custom scripts.
Monitor and debug network requests.
After reading, share your thoughts:
What other ways have you used Chrome DevTools (or similar tools in other browsers) to improve testing and troubleshoot issues?
I use it to keep an eye on the hit endpoints to make sure none of them throw an error. I may also check some of the endpoints to see if their response is the expected one. I also use a tool called Mokku that allows me to force endpoints to throw whatever error I want which is very useful.
I’m generally an dev tools always open tester when it comes to web applications, though it does on occasion change behavior just by having it open.
I still find there is always something new of value I can learn from using it, so many features to help with testing.
The simple access to copy as curl and import into postman is one I also often use alongside lighthouse.
As an FYI I have also often used it as a hiring filter, really hard to get my head around how some web testers can not be using it at all. The course Technical testing 101 I found invaluable to introductory usage real examples, if you are new to dev tools I highly recommend that course though I’m not sure when it was last updated.
I’ve used DevTools to inspect and compare code to the NHD Digital Design System, and to run Accessibility tools like Axe, but recently I’ve needed to provide more information on fixes.
These tips are perfect for me to take my analysis to the next level.
After 20+ years testing, I am never embarrassed to say every day’s a learning day.
Thank you all for the lovely feedback! I am grateful that my article is being useful for all of you. I actually wanted let people know about the devtools thanks to my colleagues who wanted me to provide them a KT on how to use it for better testing. That’s when I realized that there can be many who want to learn more on the vast usage of thr DevTools. Thanks once again!
