@currents_dev profile picture
currents.dev @currents_dev

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

Joined June 2021
  • Tweets 111
  • Following 773
  • Followers 185
28 Photos and videos
Pinned Tweet
currents.dev@currents_dev
14 Mar 2025
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. currents.dev/posts/currents-…

Currents Achieves SOC 2 Type 2 Certification

Achieving SOC 2 Type 2 Certification: A Milestone in Our Ongoing Commitment to Security and Compliance!

currents.dev
2
6
257
🎯 Orchestration coordinates workers and shards so machines pull tasks dynamically rather than running static lists, reducing idle time and imbalance.\n\nRead more at currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
1
3
41
💸 False green tests erode confidence. Tests that pass but aren't reliable increase debugging cost and slow feature delivery over time. Read more at currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
1
2
94
⚡ Parallel workers boost throughput but expose hidden dependencies. Ensure isolated contexts and unique test data to avoid collisions and flakiness. Read more at currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
1
48
🔁 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 currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
20
👀 Headed mode reveals dynamic UI problems like blocking spinners. Combine headed runs with traces, screenshots, and videos to pinpoint failures. Read more at currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
23
We just released Playwright Best Practices, the most comprehensive Playwright AI Skill yet. 👉 Check it out at github.com/currents-dev/play… #Playwright #AI #TypeScript
1
2
6
254
currents.dev retweeted
Andrew Goldis
@agoldis
Jan 27
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 linkedin.com/pulse/playwrigh… #playwright

playwright-cli: First Impressions and Key Takeaways

A review of playwright-cli - a new tool that is compatible with AI Agent Skills and allows interacting with browsers using CLI

linkedin.com
2
2
217
currents.dev retweeted
Andrew Goldis
@agoldis
Jan 27
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: changelog.currents.dev/chang…

Slack App Integration

Notify Team Members and Slack Groups about failures and flaky results Integrate Currents with Slack to receive real-time notifications and failure ale...

changelog.currents.dev
1
55
💸 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 currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
24
🤖 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 currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
25
📋 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 currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
31
🧠 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 currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
33
⚠️ 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 currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
19
📋 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 currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
13
🚀 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 currents.dev/posts/optimizin…\n\n#Playwright #TestAutomation #FrontEnd

Optimizing Test Runtime: Playwright Sharding vs. Workers

Long Playwright test runtimes slow CI pipelines. We compare Playwright workers vs. sharding, and when test orchestration becomes the better alternative.

currents.dev
18
🔧 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 currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
28
⚠️ A green CI dashboard doesn't guarantee workflows work. Passing tests can hide regressions unless analytics track trends.
13
⚠️ 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 currents.dev/posts/how-to-ru… #Playwright #TestAutomation #FrontEnd

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
25
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: currents.dev/posts/how-to-ru… #Playwright #e2e #Frontend

How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500 Tests

A reader-submitted guide sharing 14 lessons learned from writing 500 Playwright tests — essential tips for beginners to avoid common pitfalls.

currents.dev
1
88
🚦 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 currents.dev/posts/how-to-tr…

How to Track the Health of Your Playwright Test Suite

Passing tests can hide broken workflows. Understand how test automation analytics track key metrics to keep your Playwright test suite healthy.

currents.dev
26
Load more