---
title: "Comment by Michael Weber on \"Playwright - debug your tests\" | Hashnode"
description: "Great tips, Luca! Visual Studio Code integration is definitely a lifesaver compared to writing a million console logs. While local breakpoints work perfectly, t"
url: "https://hashnode.com/posts/playwright-debug-your-tests/63a2cb3a29e757b59697c803/comment/6a4e31cc07450ae4c3500bb8"
---

[Discussion](https://hashnode.com/posts/playwright-debug-your-tests/63a2cb3a29e757b59697c803)

Comment [Playwright - debug your tests](https://hashnode.com/posts/playwright-debug-your-tests/63a2cb3a29e757b59697c803)

[Jul 8](https://hashnode.com/posts/playwright-debug-your-tests/63a2cb3a29e757b59697c803/comment/6a4e31cc07450ae4c3500bb8)

Great tips, Luca! Visual Studio Code integration is definitely a lifesaver compared to writing a million console logs.

While local breakpoints work perfectly, things usually get tricky when tests fail silently in headless CI runners. I often refer to this guide on handling post-mortem tracing and debugging: [testomat.io/blog/debugging-tracing-playwright-fea…](https://testomat.io/blog/debugging-tracing-playwright-features-tips-techniques-to-running-and-debugging-tests/) because it covers how to tackle those remote container errors. Thanks for the quick guide!