Playwright Shuffle and Named Locks for Finding Order-Coupled TestsPlaywright Shuffle and Named Locks for Finding Order-Coupled Tests
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A green Playwright suite can still be order-coupled.
A test can pass only because an earlier one left the database, storage, or a shared account in the right state. Change the worker schedule and that same check looks flaky.
Playwright 1.64, released 7 October 2026, adds --shuffle. It schedules tests in a random order and prints a seed. Pass that seed on the next run to reproduce the order that failed.
Shared accounts still need an explicit boundary. test.describe.configure({ lock: 'user-settings' }) keeps tests that share the lock from running at the same time, across files and projects. Every other test stays parallel.
In the default and serial modes, that lock is held for the whole file, because those tests already run together in order. Run shuffle on a scheduled job first, and keep the seed with the failure.
• 𝗦𝗵𝘂𝗳𝗳𝗹𝗲 𝗦𝗲𝗲𝗱 — replay the failed order • 𝗡𝗮𝗺𝗲𝗱 𝗟𝗼𝗰𝗸𝘀 — one shared account, no concurrent runs • 𝗙𝗶𝗹𝗲-𝗦𝗰𝗼𝗽𝗲𝗱 𝗛𝗼𝗹𝗱 — default mode holds the lock for the whole file • 𝗪𝗼𝗿𝗸𝗲𝗿 𝗗𝗮𝘁𝗮 — own records per worker • 𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗲𝗱 𝗦𝗵𝘂𝗳𝗳𝗹𝗲 — catch coupling off the pull-request path
https://github.com/microsoft/playwright/releases/tag/v1.64.0
#SQA #SDET #TestAutomation #Playwright #SoftwareTesting #QualityEngineering #CICD #FlakyTests #TestArchitecture #DevOps
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started