Playwright stack traces provide lots of useful information, but something about them is overriding or otherwise preventing the exact failed test block and line. We should handle that so users don't have to drop break points and hunt OR trace the failure from the selector back up to the block/line.
Note: Could be related to issue 95 as this wasn't a problem in a VS Code project that used MSTest setup/teardown.
Playwright stack traces provide lots of useful information, but something about them is overriding or otherwise preventing the exact failed test block and line. We should handle that so users don't have to drop break points and hunt OR trace the failure from the selector back up to the block/line.
Note: Could be related to issue 95 as this wasn't a problem in a VS Code project that used MSTest setup/teardown.