Time & Async

Some things a program asks for are slow — fetching data across the internet takes an eternity in machine time. If JavaScript simply waited, the whole page would freeze with it: no clicks, no typing, no scrolling, until the data arrived. Async is how one worker stays responsive while slow things cook. And since every single Playwright command works this way, an automation tester lives and breathes this phase.

JavaScript does exactly one thing at a time — it is single-threaded. Code that runs one step after another, each step waiting for the previous one, is called synchronous. That’s fine until one step is slow (like fetching data across the internet): synchronous waiting would block everything — frozen page, dead buttons.

The fix is to be asynchronous, or non-blocking: start the slow job, immediately move on, and get called back when the result is ready. Picture one waiter serving a whole café: they don’t stand at your table while the kitchen cooks (blocking); they take your order, serve others, and return when the bell rings (non-blocking). The bell system is JavaScript’s event loop.

This single idea is the heart of the browser AND of Node.js — and of every Playwright test you’ll ever write (they’re async from the first line). It’s also where the visualizations in this app do their finest work.