wait-strategy

Prioritize implicit waits over explicit waits in UI automation.

176|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/DanielSuo117/velocitai --skill wait-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wait-strategy
Source: https://github.com/DanielSuo117/velocitai/tree/main/zh/skills/wait-strategy
Command: npx skills add https://github.com/DanielSuo117/velocitai --skill wait-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implicit waits dominate to reduce flakiness in UI automation; explicit waits are reserved for known slow paths.

Core Features & Use Cases

  • Implicit waiting defaults across the page lifecycle to reduce manual timeout tuning.
  • Explicit waits are applied only for slow paths like large uploads, long polling, or redirects.
  • Provides guidance for configuring DEFAULT_TIMEOUT and integrating with page fixtures.

Quick Start

Configure a global implicit timeout and prefer implicit waits; use explicit waits only when slow paths are encountered.

Frequently Asked Questions about wait-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce flakiness in Playwright UI automation tests?

Reduce UI automation flakiness in Playwright by prioritizing implicit waits with a global DEFAULT_TIMEOUT. This governs page lifecycle interactions automatically, minimizing manual timeout tuning and intermittent test failures.

What is the best wait strategy for slow paths like large uploads in web testing?

The best wait strategy reserves explicit waits for slow paths like large uploads, long polling, or external redirects. Implicit waits handle standard interactions, while explicit waits target known delays to streamline execution.

When should I use explicit waits instead of implicit waits in test automation?

Use explicit waits in test automation only for known slow paths such as large uploads, long polling, or external redirects. Implicit waits should dominate standard page interactions to reduce flakiness.

Does the implicit wait strategy work with Playwright page fixtures?

Yes, the implicit wait strategy integrates with Playwright page fixtures by applying a global DEFAULT_TIMEOUT. This enforces implicit waiting defaults across the page lifecycle, requiring explicit waits only for slow paths.

Why should I avoid time.sleep in Playwright web-testing scripts?

Avoid time.sleep in Playwright web-testing scripts because it causes rigid delays and flakiness. Enforcing a global DEFAULT_TIMEOUT with implicit waits handles dynamic loading naturally, while explicit waits manage slow paths.