TEST006infoPro

e2e-console-capture

E2E tests should capture console errors to catch silent JavaScript failures.

Applies to: TypeScript

Why this matters

Playwright tests can pass even when the app throws JavaScript errors, because UI assertions don't check the console. Without capturing console.error and failed assertions, you miss: unhandled exceptions, React errors, network failures, and application bugs that don't cause visible UI changes. Set up automatic console capture in a shared fixture to catch these issues early.

Catch it before it ships

pip install stablestack # or: npx stablestackstablestack # scans your project, TEST006 includedstablestack explain TEST006

TEST006 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.

False positive in your codebase? Suppress a single line with # noqa: TEST006

More Testing checks

skipped-tests

Test is marked as skipped.

async-mock-issues

Async function mocked incorrectly.

duplicate-test-helpers

Test helper function may be duplicated across test files.

e2e-test-duplication

E2E test contains duplicated code that should use shared helpers

missing-e2e-tests

Web projects should have Playwright E2E tests to catch console errors and broken pages.

playwright-test-slow-misuse

Detects incorrect test.slow() usage that silently skips tests.

playwright-wait-for-timeout

waitForTimeout() in tests waits for arbitrary time instead of content/state.

instant-visibility-before-assert

safeVisible() or isVisible() result used in expect() — instant checks don't wait for elements to render, causing flaky tests.