currents.dev @currents_dev

Testing CI intelligence platform - troubleshooting, analytics and performance for humans and agents. currents.dev Vancouver, BC, Canada Joined June 2021

Tweets

122
Followers

191
Following

769
Likes

122

currents.dev @currents_dev

a day ago

⭐️ Currents is proud to sponsor OSS projects and builders: github.com/mswjs github.com/vitalets

0 1 1 39 1

View Details

📈 Test analytics are essential: monitor per-file durations, failed retries, and shard imbalance. Use data to decide when to move from workers to sharding to orchestration.\n\nRead more at currents.dev/posts/optimizi…\n\n#Playwright #TestAutomation #FrontEnd

0 1 3 65 0

View Details

currents.dev @currents_dev

a month ago

📈 Tests are living code - without monitoring they rot. Track flaky trends, test times, and evolve the suite. Read more at currents.dev/posts/how-to-r… #Playwright #TestAutomation #FrontEnd

0 0 1 43 0

View Details

currents.dev @currents_dev

a month ago

🚫Hard-coded test inputs kill Playwright reliability. Randomize to thrive. Read more at currents.dev/posts/how-to-r… #Playwright #TestAutomation #FrontEnd

0 0 2 47 1

View Details

Andrew Goldis @agoldis

2 months ago

What does "skipped" mean - test statuses review across popular JavaScript runners currents.dev/posts/test-sta…

1 1 5 187 0

View Details

currents.dev @currents_dev

2 months ago

Fix #Playwright CI failures without leaving your IDE! Introducing Currents IDE extension: - Bring detailed test results directly from CI to VS Code / Cursor and other IDEs - No switching between tabs and file downloads - Open remote trace files directly in the IDE - Smart context for AI fixes - generated execution steps, network logs, error details, test history and cross-run intelligence. 👉 currents.dev/changelog/ide-…

0 1 4 233 0

View Details

currents.dev @currents_dev

2 months ago

0 0 1 173 0

View Details

currents.dev @currents_dev

2 months ago

New: Send test failure details from Currents straight into Linear — including error stack, trace details, flake history + comments and annotations. For efficient CI failures troubleshooting - by humans or agents. See 📹 in 🧵. currents.dev/changelog/inte…

1 2 3 112 0

View Details

Hackmamba @hackmamba

2 months ago

The useful question about staging and production is what each environment is for, and whether your Playwright configuration reflects that purpose. Staging absorbs risk, so it takes anything that mutates state, fires real emails, or triggers a payment. Production validates that the live system works for real users, which keeps it to read-path flows and a small set of high-signal checks. Most suites blur the two and run one config against both. That’s how a green test ends up hiding a real production break. This article by @currents_dev turns that into a concrete framework: a decision table for placing any test, the configuration that should differ by environment, and the failure modes that show up when teams skip the distinction. How clearly are these two environments separated in your setup? Article link in the comments.

1 1 1 132 1

View Details

Hackmamba @hackmamba

2 months ago

If your team has ever debated "should we mock this or hit the real API," the honest answer is that it depends on five things: - How critical the flow is. - The cost of getting it wrong. - Who controls the API. - Whether a formal contract exists. - What real testing actually costs you in time and quota. This article by @currents_dev breaks that decision down across a five-level spectrum, from no mocking at all to schema-validated and contract-tested mocks. It also covers parts like webhook testing, idempotency keys for real integration runs, and how to clean up sandbox data when ten parallel CI runs share the same Stripe test account. If you're making suite-wide decisions rather than writing one-off tests, this one is for you. Article link in the comments.

1 1 6 141 1

View Details

currents.dev @currents_dev

3 months ago

📇 Avoid brittle test data: generate unique values per run, mock APIs when possible, and clean up test data to prevent run-to-run collisions. Read more at currents.dev/posts/how-to-r… #Playwright #TestAutomation #FrontEnd

0 0 1 90 1

View Details

currents.dev @currents_dev

4 months ago

🎯 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/optimizi…\n\n#Playwright #TestAutomation #FrontEnd

0 1 3 58 0

View Details

currents.dev @currents_dev

4 months ago

💸 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-r… #Playwright #TestAutomation #FrontEnd

0 1 2 104 0

View Details

currents.dev @currents_dev

6 months ago

⚡ 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-r… #Playwright #TestAutomation #FrontEnd

0 0 1 56 0

View Details

currents.dev @currents_dev

7 months ago

🔁 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/optimizi…\n\n#Playwright #TestAutomation #FrontEnd

0 0 0 28 0

View Details

currents.dev @currents_dev

7 months ago

👀 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-r… #Playwright #TestAutomation #FrontEnd

0 0 0 31 0

View Details

currents.dev @currents_dev

8 months ago

We just released Playwright Best Practices, the most comprehensive Playwright AI Skill yet. 👉 Check it out at github.com/currents-dev/p… #Playwright #AI #TypeScript

2 2 5 272 2

View Details

Andrew Goldis @agoldis

8 months ago

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/playwrig… #playwright

0 2 3 223 1

View Details

Andrew Goldis @agoldis

8 months ago

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/changelog/slac…

0 1 1 62 0

View Details

currents.dev @currents_dev

8 months ago

💸 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/optimizi…\n\n#Playwright #TestAutomation #FrontEnd