---
title: "Discussion on \"Playwright - debug your tests\" | Hashnode"
description: "Discussion on \"Playwright - debug your tests\". VsCode Extensions"
url: "https://hashnode.com/posts/playwright-debug-your-tests/63a2cb3a29e757b59697c803"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Playwright - debug your tests](https://puppo92.hashnode.dev/playwright-debug-your-tests?utm_source=hashnode&utm_medium=feed)

VsCode Extensions

Dec 21, 2022 · 4 min read · puppo92.hashnode.dev  
Read the article

-   [#playwright](https://hashnode.com/tag/playwright)
-   [#e2e](https://hashnode.com/tag/e2e)
-   [#vscode-extensions](https://hashnode.com/tag/vscode-extensions)

## Written by

[Luca Del Puppo](https://hashnode.com/@Puppo92)

@Puppo92 · Treviso, IT

  
[View profile](https://hashnode.com/@Puppo92)

Microsoft MVP, Google Developer Expert, GitKraken Ambassador, Senior Software Developer at NearForm and JavaScript enthusiastic.

Full Stack Developer and JavaScript and TypeScript enthusiastic.

## Responses 1

Markdown supported · ⌘↵ to post

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

[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!