Playwright's auto-wait engine waits for elements to be attached, visible, stable, and enabled before acting, and it waits for navigation when appropriate. That means most tests don't need explicit sleeps at all. When you do need to wait, prefer expect(locator) assertions such as toBeVisible, toHaveText, toHaveURL, toHaveValue, toHaveAttribute, toHaveCount, toBeChecked, toBeDisabled, and toBeFocused. These auto-retry up to a configurable timeout and produce much better error messages than arbitrary sleeps.
Some patterns that frequently cause flaky tests are worth avoiding. page.waitForTimeout() should be a last resort, reserved for genuinely non-deterministic animations or third-party widgets you can't otherwise signal. waitForLoadState('networkidle') is rarely reliable because polling apps never actually go idle; prefer waiting for an explicit signal such as a spinner becoming hidden or a specific API response. When the next click triggers navigation, race the click against waitForURL with Promise.all so the navigation event isn't lost. For conditions that don't map to a built-in matcher, expect.poll runs a function repeatedly until it passes.
Soft assertions let you collect multiple failures in a single run via expect.soft, which is useful for broad health checks where one failure shouldn't stop the rest of the report. Grouping steps with test.step('create report', async () => { ... }) produces a cleaner HTML report and makes failures easier to attribute. For dynamic UI like toasts or status banners, target the role='status' element and assert on a regex with toContainText, since exact text often varies by locale. test.setTimeout and test.describe.configure({ timeout }) let you extend limits for slow flows without making the whole suite slow.