Get started with end-to-end testing: Playwright | Episode 5 - Debugging Tests

Let’s learn how to debug our failing test right in VS Code with live debugging and break points as well as debugging using the show trace option to see a full trace of our test. From the trace we can see a DOM snapshot of each action of our test and use the pick locator feature to ensure we are using the right locator for the element that’s failing.

Playwright Series Playlist:

Chapters:
00:00 In this episode
00:28 Debugging in VS Code
01:25 Locator docs
01:32 Setting Breakpoints
02:33 Using the Trace Viewer
05:12 Up Next: Running tests on CI

Links:
VS Code Extension:
Playwright docs VS Code:
Playwright’s trace viewer:
Playwright on Discord:

#playwright #playwrightdev #vscode

[Norfeldt]

I'm very please to see these videos covering a lot of fantastic features. I am hoping that future videos will cover the first major bump that many devs faces - writing tests for pages that requires auth. I am personally hoping to see a way of reusing the auth session between my tests..

[BeheadedKamikaze]

Thanks for the guide! 5:15 I've never heard anyone pronounce "commit" as "comet" before. 😄 Typically one would say "com" "mitt".

[ShobharaniSeeram]

I am getting gcc error file name missing after -o how to fix this