test-debugging-specialist

Fix assertion errors and element lookup failures by reproducing the issue in isolation, inspecting the DOM or application state, and validating mock behavior. This approach works across Vitest and Playwright setups to quickly restore test stability.

Resolve Playwright timeouts by using the Playwright Inspector to inspect the DOM, capturing screenshots to verify element visibility, and adding console logging to trace application state during the test run.

Isolate a failing test by running the specific test file independently rather than the full suite. This reduces interference, allows targeted console logging, and helps reproduce exact failure conditions quickly.

Verify mock behavior by validating mock interactions and assertions directly within the isolated test run. Use console logging to output mock call data and confirm the mocked functions receive expected arguments.

Yes, this systematic debugging approach applies to unit, integration, and end-to-end tests. It handles assertion errors, element lookup failures, timeouts, and mock-related issues across both Vitest and Playwright environments.