---
title: "Comment by Michael Weber on \"Guide to Playwright Debugging – Tips and Techniques\" | Hashnode"
description: "Great read! The tip about using PWDEBUG=console to expose the global playwright object in Browser DevTools is so underrated. Being able to evaluate selectors li"
url: "https://hashnode.com/posts/guide-to-playwright-debugging-tips-and-techniques/6710dc8f273e2adf34906e9d/comment/6a853eb75cb721280c59e216"
---

[Discussion](https://hashnode.com/posts/guide-to-playwright-debugging-tips-and-techniques/6710dc8f273e2adf34906e9d)

Comment [Guide to Playwright Debugging – Tips and Techniques](https://hashnode.com/posts/guide-to-playwright-debugging-tips-and-techniques/6710dc8f273e2adf34906e9d)

[Michael Weber](https://hashnode.com/@weberstmichael)

[Aug 19](https://hashnode.com/posts/guide-to-playwright-debugging-tips-and-techniques/6710dc8f273e2adf34906e9d/comment/6a853eb75cb721280c59e216)

Great read! The tip about using PWDEBUG=console to expose the global playwright object in Browser DevTools is so underrated. Being able to evaluate selectors like playwright.$(selector) directly in the console saves a lot of trial and error when dealing with shadow DOM or dynamic locators.

When managing larger E2E suites synced with platforms like Testomat.io, having a solid debugging loop locally keeps build times fast and flaky tests to a minimum.

If readers want to explore more tips on actionability checks and debugging setup, check out this guide on playwright inspector. [testomat.io/blog/debugging-tracing-playwright-fea…](https://testomat.io/blog/debugging-tracing-playwright-features-tips-techniques-to-running-and-debugging-tests/)