TEST007infoPro

missing-e2e-tests

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

Applies to: JSON

Why this matters

Web applications can have silent failures - JavaScript errors, broken API calls, and rendering issues that don't cause obvious crashes. Without E2E tests that check for console errors, these bugs ship to production unnoticed. Playwright tests can load your pages and verify no errors occur, catching issues before users do.

Catch it before it ships

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

TEST007 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: TEST007

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

e2e-console-capture

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

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.