automation-best-practices

Flaky automation scripts often fail due to arbitrary delays and brittle selectors. Replace hard-coded waits with deterministic DOM and network settling helpers, use stable semantic selectors instead of fragile XPath or positional selectors, and implement conditional waits that verify element state before interacting. This reduces retry rates and improves reliability.

Prefer stable, accessible selectors that target semantic attributes like data-testid or aria-labels over CSS class names or XPath that break with UI changes. Semantic selectors remain resilient across styling updates and reduce maintenance overhead when refactoring automation scripts.

Replace arbitrary timeouts with intelligent wait strategies: use DOM settling to verify element visibility, network interception to confirm data loads, and conditional checks before actions. Batching evaluations and avoiding pressSequentially() in favor of fill() further improves performance and reduces flakiness.

Apply anti-detection features minimally and only when necessary to avoid detection triggers. Focus first on efficient, maintainable patterns: direct URL building, batched evaluations, and lightweight session management. Over-reliance on anti-detection can degrade performance and introduce maintenance burden.

Use a structured review checklist covering selector stability, wait determinism, batched DOM extractions, and SDK pattern compliance. Modular code structure, clear separation of concerns, and adherence to no arbitrary delays enforce maintainability and catch reliability issues before deployment.

Yes. Refactor existing Playwright scripts by replacing waitForTimeout with conditional waits, converting brittle selectors to semantic alternatives, and restructuring extractions into batched operations. Teams typically reduce retry rates substantially by applying these patterns incrementally to legacy automation code.