Trace a request from the browser to the server and back, then gather the evidence a developer needs from Chrome DevTools: the element, the console error, the failing request with its status and payload, what the site stored, and the page at a phone width. Test forms and layouts and run an exploratory session on the cart of the Shelf practice shop. For learners who can write a test case and a bug report; no networking or coding knowledge needed, a desktop computer with Chrome is. Course 5 of the QA Engineer Path.
Course 5 of 13 in the QA Engineer Path
Trace a request from the browser to the server and collect evidence in DevTools.
The full outline. Lessons open when the course does.
Section: QA Engineer Path
Next on the path: API Testing with Postman
Artsiom Rusau – QA engineer and course author. He has tested software since 2019 and has taught software testing since 2020.