currents.dev

Debug, troubleshoot and analyse parallel CI tests in Cloud. Cypress and Playwright.

[currents.dev @currents_dev]

We are excited to announce that we have successfully obtained our SOC 2 Type 2 certification! 👏

We look forward to continuing to prioritize security and compliance as we grow.

https://t.co/IrEipRc3Hh

[currents.dev @currents_dev]

💸 False green tests erode confidence. Tests that pass but aren't reliable increase debugging cost and slow feature delivery over time.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

⚡ Parallel workers boost throughput but expose hidden dependencies. Ensure isolated contexts and unique test data to avoid collisions and flakiness.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

🔁 The real problem isn't parallelism - it's scheduling. Use duration-aware orchestration that runs long tests early to avoid straggler shards and idle machines.\n\nRead more at https://t.co/v8cgfgbJwd\n\n#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

👀 Headed mode reveals dynamic UI problems like blocking spinners. Combine headed runs with traces, screenshots, and videos to pinpoint failures.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

We just released Playwright Best Practices, the most comprehensive Playwright AI Skill yet.

👉 Check it out at https://t.co/DlE1R67AAw

#Playwright #AI #TypeScript

[Andrew Goldis @agoldis]

I took playwright-cli for a ride and shared my first impressions:

- great addition to playwright ecosystem
- be careful with token usage
- it is not a replacement for traditional testing
- great lightweight skills-baked alternative to MCP

https://t.co/O2lXFJg7qz

#playwright

[Andrew Goldis @agoldis]

Let the right people know if there's a problem with a test. - notify test owners when a smoke test failed on `main` branch - notify a squad about a flaky test, including failure and flakiness details Check out the details in our new Slack integration:

https://t.co/pOknReJRqQ

[currents.dev @currents_dev]

💸 Save CI spend by combining orchestration with spot instances. Orchestration can migrate in-flight tests when spot VMs terminate, keeping runs fast and cheap.\n\nRead more at https://t.co/v8cgfgbJwd\n\n#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

🤖 Use AI to surface recurring flakiness, highlight slow suites, and scaffold scenarios. It speeds diagnosis but doesn't replace isolation and async discipline.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

📋 Quick checklist: start with workers; shard when a single machine can't hit runtime goals; use orchestration to fix uneven shard timings and provisioning hiccups.\n\nRead more at https://t.co/v8cgfgbJwd\n\n#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

🧠 fullyParallel: true enables test-level parallelism but disallows per-file shared fixtures and sequential assumptions. Refactor stateful setup before turning it on.\n\nRead more at https://t.co/v8cgfgbJwd\n\n#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

⚠️ Flaky failures often come from CPU contention when too many workers run on one machine. Match worker count to physical cores to reduce timeouts and flakiness.\n\nRead more at https://t.co/v8cgfgbJwd\n\n#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

📋 Quick checklist for stable Playwright suites: organize tests, create fresh contexts per test, await all actions, isolate data, use traces and retries.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

🚀 Long CI runs usually mean infrastructure limits, not bad tests. Start with workers, move to sharding when machine capacity is maxed, and add orchestration to remove static imbalance.\n\nRead more at https://t.co/v8cgfgbJwd\n\n#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

🔧 Playwright actions are async. Omitting 'await' lets tests proceed before actions finish, producing intermittent, CI-only failures that are hard to debug.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

⚠️ A green CI dashboard doesn't guarantee workflows work. Passing tests can hide regressions unless analytics track trends.

[currents.dev @currents_dev]

⚠️ Flakiness often comes from shared browser context, order dependencies, or test data collisions. Isolate contexts and data per test to reduce noise.

Read more at https://t.co/SRSYgyXvqy

#Playwright #TestAutomation #FrontEnd

[currents.dev @currents_dev]

Beginner to Playwright? This new reader-submitted article is for you.

A community member shared the lessons learned across 500+ tests — all the pitfalls, fixes, and habits they wish they knew earlier.

👉 Full article: https://t.co/BR01Cez99g

#Playwright #e2e #Frontend

[currents.dev @currents_dev]

🚦 Green CI doesn’t guarantee a healthy Playwright suite: Flakiness, slow tests, and gaps in workflow coverage often stay hidden behind passing runs.

🔍 Read: How to Track the Health of Your Playwright Test Suite

https://t.co/qTrCshqdQ8

[currents.dev @currents_dev]

https://t.co/D5FoUtQIPB

#flakiness #plawyright #E2E