10 Playwright Best Practices for Reliable Tests

Creating a Resilient Automation Suite

Test automation only provides value if the results are trustworthy. If your test suites are flaky (failing randomly due to load speeds or sync issues), developers will ignore the results. Here are the top 10 best practices implemented by world-class QA automation engineers to maximize Playwright stability.

1. Never Use Hardcoded Wait Timeouts

Adding page.waitForTimeout(5000) is a bad anti-pattern. If a page loads in 1 second, you waste 4 seconds. If it takes 6 seconds on a busy CI server, your test fails.
Solution: Rely on Playwright's built-in auto-waiting and web assertions, which poll dynamically:

// ❌ AVOID
await page.waitForTimeout(5000);
expect(await page.locator('.success-banner').isVisible()).toBe(true);

//  PREFER
await expect(page.locator('.success-banner')).toBeVisible({ timeout: 5000 });

2. Keep Tests Completely Independent

Never rely on Test B executing after Test A finishes to use its logged-in state or created resource. Tests must run in any order, and in parallel.
Solution: Seed database states via API requests or use a global login configuration to setup states beforehand.

3. Assert State, Not Action Outcomes

Avoid asserting that a click event succeeded. Instead, assert that the target page element is now visible.

// Better assertion
await page.getByRole('button', { name: 'Submit' }).click();
await expect(page.locator('#success-message')).toBeVisible();

4. Use Soft Assertions for Non-Critical Checks

If a page contains multiple footer links or layout parameters, use soft assertions. If a soft assertion fails, the test continues so you can see all failures at the end rather than blocking early.

await expect.soft(page.locator('.footer-copyright')).toContainText('2026');
await expect.soft(page.locator('.support-link')).toBeVisible();

Conclusion

Writing reliable E2E tests is easy when you leverage the framework's native architecture. By avoiding sleep timeouts, keeping tests isolated, and choosing semantic role locators, you will create a zero-flake CI/CD pipeline.