Changelog

Slack notifications should tell you what happened without turning into another noisy feed. This update makes run updates easier to scan, keeps threaded messages current, and gives you direct paths from a failure to the next step.

• See run status at a glance — every Slack notification now uses status colors, so failed, passing, cancelled, timed-out, and in progress runs are easier to spot.
• Keep threads short and updated — the first message in a run thread updates as the run progresses. Replies only appear for events that need attention, such as failed tests, flaky tests, cancellations, and timeouts.
• Get accurate final results — multi-group runs now send one final summary per destination, and Slack messages update when late test results change the totals.
• Fix failures from Slack — failure messages include a "Fix with AI" action that opens the existing AI-assisted troubleshooting flow with the relevant run and test context.
• Open the right view in Currents — links from Slack notifications now open Run Summary with the relevant failed, flaky, and group filters already applied.
• Control when success messages arrive — send pass-only notifications to a separate channel, or receive a recovery message when a branch succeeds after a failure.
• Send scheduled reports to Slack — automated reports can now post a compact Slack card with run and test totals, success rate, duration, trends, and links to the filtered Insights views.

References

• Slack App
• Automated Reports

We've redesigned our pricing to better match how teams actually use Currents. Test suites are growing faster than ever, especially with AI-assisted development, and our old pricing structure didn't keep up. Rates are lower across the board, volume discounts are bigger, and we removed most of the friction that made purchasing and scaling harder than it needed to be. User limits, overage penalties, and needing a sales call for enterprise features were all pain points we heard about repeatedly. This update addresses all of them.

• Team plan renamed to Scale with cheaper per-test rates and bigger volume discounts. Self-serve tiers now go up to 500K tests/month (previously 150K).
• New Business plan with SSO, SCIM, and other enterprise features available on self-serve. No sales call needed.
• 50 users included on both Scale and Business (up from 10). Read-only guest users are now free and unlimited.
• Fairer overage billed at the same per-test rate as your plan. You can also upgrade mid-cycle and overage recalculates immediately at the new rate.
• Yearly usage pooling — yearly plans now pool your test volume for the full year instead of resetting monthly. We also increased the yearly discount from 1 month free to 2 months free.

Existing Team customers are being automatically moved to Scale with no action needed.

Read the full announcement: Introducing Currents' New Pricing

Currents is now available right in your editor. The new IDE extension brings CI runs, failure details, and troubleshooting tools into VS Code, Cursor, and compatible forks — no need to open the dashboard.

• CI runs in your sidebar — browse the latest runs, filter by branch, author, tag, or status, and see failures grouped by pull request.
• Fix CI failures without leaving the IDE — the "Fix with agent" action sends the failure to your AI assistant, scoped to a single test, a spec file, or a whole run.
• Rich context for AI agents — each failure ships with the full error message, stack trace, test history, and an error-context snapshot: the page accessibility tree, console output, and network logs captured at the moment of failure. Agents troubleshoot from evidence, not guesses.
• Inline trace files — open the Playwright trace for a failed test in an editor panel to step through actions, inspect DOM snapshots, and read console and network logs manually.
• On-demand context via Currents MCP — the extension automatically registers the Currents MCP server, so agents can fetch additional details about runs, tests, and history as they work — no manual setup.

Install it from the VS Code Marketplace or the Open VSX Registry (Cursor and other VS Code forks), or search for "Currents" in your editor's Extensions panel. You'll need a Currents account and an API key.

References

• Documentation
• VS Code Marketplace
• Open VSX Registry

Share Tests Failure details with your team in Linear directly from Currents. Currents injects all the necessary details about test failures for for humans and agents. No tab switching, no copy-paste.

Enable our native integration with Linear to create or link issues directly from Currents. Once enabled, you can see and edit Linear Issues associated with your tests directly in Currents.

• Full Details for Effective Debugging - Currents injects all the necessary details required to troubleshoot test failures.
• Create or Link Existing Issues - add multiple failures to the same issue, track already affected tests without switching tabs or losing focus.
• Secure, Configurable — based on native secure OAuth integration with Linear, connects once for your entire workspace and configured per project.

When a test fails, the Linear icon is right there. Click it, create a new issue or attach an existing one, and move on. Stack traces, run metadata, and Currents links go with it.

Built to replace your manual Linear workflows:

• Pick a team, project, assign a teammate
• Reference failure details
• Add extra details - done!

References

• Documentation
• Currents App in Linear Directory

We've released @currents/playwright 2.0 with full support for Playwright 1.60 and newer.

We've updated the orchestration workflow to use two commands for better control over test discovery and execution.

• Playwright 1.60+ support: Now fully compatible with the latest Playwright versions
• Improved workflow: Separate test discovery (pwc-p discover) from orchestration execution (pwc-p run)
• Better filtering: Apply Playwright filters (--grep, --last-failed, --project) before orchestration

⚠️ Migration Required

If you're using Playwright 1.60+, you must upgrade to @currents/playwright 2.0. The orchestration workflow has changed to a two-step process. See the migration guide for detailed instructions.

• Orchestration Setup
• CI/CD Examples

You can now add guests to your Currents organization without consuming a billable seat. This makes it easier to bring in stakeholders, reviewers, and cross-functional teammates while keeping paid seats reserved for people who need full write access.

• Invite teammates as Guests even when billable seats are full
• Keep billing and seat limits focused on billable members only

This should make it much easier to collaborate with engineering managers, QA leads, support teams, and other stakeholders who need visibility into test outcomes without taking up a paid seat.

• Manage Team
• Billing & Usage

Organization admins can now set a hard cap on how much extra usage is allowed beyond your plan limit before Currents pauses recording new results.

• Enable Limit Extra Usage in Billing & Usage
• Set a cap as a percentage of your plan limit (e.g. 0%, 50%, 100%)
• CI pipelines and test runners keep running — only recording pauses
• Recording resumes automatically when the usage cycle resets, the cap is raised, or the plan is upgraded
• Available now for all customers on extra usage plans

Enabling extra usage cap

Previously, exceeding your plan limit meant accumulating extra usage fees with no upper bound. With the new cap, you decide the ceiling up front — set it to 0% to stop the moment you hit your plan limit, or to 50% to allow a buffer (for example, up to 15,000 recordings on a 10,000 plan) before recording is paused.

When the cap is reached, your tests continue to run in CI without disruption — Currents simply stops ingesting new results until the next cycle, or until you adjust the cap or upgrade the plan.

This makes budgets predictable while keeping pipelines unaffected.

• Capping Extra Usage documentation
• Billing & Usage

Teams use Currents Actions to conditionally skip, tag, or quarantine tests, so PRs stay green and teams aren't blocked on known flakes or temporary exceptions.

In this release we've made Actions easier to trust and debug by surfacing affected tests in two places.

• On each Action, you can see which tests it hit in your chosen window, open recent executions, and tie them back to the commits they ran on.
• Actions → Affected tests has a project-wide list of tests touched by Actions, with filters and a drill-down so you can see which Actions fired and when—without hopping or guessing.

See which tests each Action touches

• Open any Action and scroll to Affected Tests to see tests that matched in your chosen time range
• Tune the lookback window to focus on recent runs or a longer history
• Expand a test to view recent executions where this Action applied

See all the tests affected by an Action

Open Actions → Affected tests for a project-wide view: every test that matched an Action in your lookback period, with the Actions that applied on each test in one place.

• Use Action status and Action type filters to narrow to active rules, skips, quarantines, tags, or other behaviors you care about
• Search by test title, spec file, or action name to jump to a specific case

This makes it easier for admins and contributors to reason about Actions in context: fewer surprises in CI and faster answers when someone asks, "which tests is this rule actually hitting?"

• Using Currents Actions
• Actions reference

Action Notifications help your change or approach expiration -- before surprises hit your pipeline.

Configure delivery once per project, then get alerts in Slack, email, or both, only for the lifecycle events you care about.

• Slack — Send to a single project channel (uses your existing Slack connection); pick which events trigger a message
• Email — Notify the action creator, org admins, and actions admins, plus optional extra addresses; same event controls as Slack
• Fine-grained events — Choose from creation, disable, re-enable, archive, expiring soon (advance warning before expiration), and expired
• Where to configure — Actions → Settings in the dashboard, alongside the rest of action management (separate from run-level Slack notifications)
• Available now for organizations using Actions

Open Actions → Settings, connect or confirm Slack if you use a channel, turn on Email if you want inbox alerts, then select events. Teams that rely on time-boxed quarantines or expiring skips can lean on expiring soon and expired so ownership and cleanup stay visible without manual polling.

• Documentation

You can now delegate action management without granting full admin access. The new Actions Admin role gives team members the ability to create, edit, and delete Actions.

This role is ideal for QA leads, DevOps engineers, or team members who need to configure test actions without full administrative privileges. Admins can invite new members as Actions Admins or update existing member roles from the Organization Settings page.

Read more about permissions and roles

• Team Management Documentation

Introducing Test Suite Size, a new analytics view that helps you track how your test suite evolves over time. Whether you're expanding coverage, refactoring tests, or debugging unexpected changes, this view gives you complete visibility into your test suite's composition.

• Track unique test cases and spec files discovered across all CI runs
• See exactly when and what tests were added or removed from your suite
• Monitor test growth by branch, tag, or team with flexible grouping
• Use rolling presence mode to smooth daily fluctuations from partial runs
• Drill down into any period to see the specific tests that changed
• Available now for all customers

Unlike run-level metrics that show tests per individual execution, Suite Size aggregates unique tests across all runs in each period. This means you get an accurate picture of your actual test coverage—not just what ran in a single CI job.

The expandable metrics table lets you click into any time period and see exactly which tests were newly detected or no longer running. Combined with grouping by Playwright tags, Git branches, or test groups, you can track coverage evolution across different parts of your codebase.

For teams with tests that don't run every day (scheduled tests, branch-specific tests, or selective execution), the Rolling Presence mode provides a stable view by counting tests seen within a configurable window—helping you distinguish real changes from normal variance.

• Test Suite Size Documentation
• Related: Run Size Analytics

Notify Team Members and Slack Groups about failures and flaky results

Integrate Currents with Slack to receive real-time notifications and failure alerts directly in your team's channels.

The new Slack App helps teams stay informed about test results without leaving their workflow.

• Threaded run notifications that keep channels organized
• Individual test notifications for failed or flaky tests
• Annotation-based mentions to notify the right people from test code
• UI-configured mention rules to route failures to the right teams
• Flexible filtering by git branch, tags, test title, and file path
• Up to 10 destinations per project with independent configuration
• Available now for all customers

Configure exactly when and how you're notified. Set up run notifications to alert on:

• all runs
• only failures, or
• only flaky tests.

Add individual test notifications to get detailed failure context with error messages and direct links to the Currents dashboard.

Configure Test or Run Slack notifications

Route failures to the right people or teams using mention rules. Define conditions like test file path or tags, then specify who gets notified—by email, Slack handle, or user group.

Mention test owners or teams when a test fails

You can also add notify:slack annotations directly in your test code to mention specific users when tests fail.

Use Playwright Annotations to configure Slack notifications

• Slack App documentation
• Playwright Annotations guide

We’ve upgraded our automated reporting system to give you more flexibility and control! Previously, each project supported only a single automated report. Now you can create and manage multiple reports within the same project — each with its own settings, schedule, and recipients.

✨ What’s New

• Multiple Reports: Create as many automated reports as you need per project.
• Custom Labels: Give each report a clear name — it will also appear as the email subject line.
• Report Management: Easily enable, disable, or archive reports directly from the new Reports dashboard.

We’ve been quiet over the last three months, focusing on delivering major improvements to our platform. This update covers a lot — use the list below to jump to what matters most.

• Analytics Engine - faster, more granular, scalable, and supporting upcoming features
• Test Explorer - new columns, new API, new controls
• Error Explorer - making sense of Playwright errors
• Custom Metrics - report any custom metric to Currents
• Data Redaction for Trace Files
• Jira Integration Improvements
• MCP
• UI changes

New Analytics Engine

We’ve completed a major refactor of our analytics engine. Over 800 million rows were migrated to a new ClickHouse cluster — smoothly and without major incidents.

Results:

• Sub-100ms P90 latency;
• More detailed, real-time insights (see Test Explorer and Error Explorer)

This overhaul was essential to meet growing demand for fast, accurate, and granular data. The new infrastructure also unlocks several upcoming capabilities:

• AI-powered insights across Currents Dashboard, GitHub PRs, CLI, Slack, email, and reports
• Enhanced context for AI workflows — test history, health metrics, and trends
• Flexible, expressive querying for fully customizable reports
• Real-time health data for powering Currents Actions, MCP, and REST API integrations

Test Explorer Improvements

Test Explorer remains one of our most-used features, helping teams quickly identify unstable or flaky tests. With the recent release, it now goes beyond snapshots to reveal trends and behavioural changes over time. You can now easily see:

• Which tests recently started to flake or fail
• Whether your fixes actually reduced failures

• Failure Rate Change — shows how failure rates shifted between two periods (e.g., last 30 days vs. previous 30 days)
• Flakiness Rate Change — compares test instability over time

Read more in Test Explorer documentation.

In addition, we’ve introduced a new /tests HTTP REST API resource that allows you to fetch Test Explorer data programmatically.

Making Sense of Playwright Errors with Error Explorer

CI pipelines generate a flood of test results, and meaningful insights are often buried in noise. Error Explorer classifies and enriches Playwright errors, transforming raw messages into structured, searchable data.

For example consider exploring the top errors affecting your runs and seeing this:

Error: expect(locator).toBeVisible() failed

This message is too generic — it can be associated with different CSS selectors and doesn’t tell the full story, nor does it allow you to take action to actually remove the errors. Wouldn’t it be better to have a more precise, application-aware data? For example:

• What CSS selectors or components cause the most CI failures?
• Are login issues due to hidden or disabled buttons?
• How many failures are infrastructure-related vs. actual test issues?

When a test fails, the raw error message and stack trace are parsed by Currents’ Error Classification Engine. It enriches every captured test error with structured fields that turn unstructured text into searchable, tokenized data.

• Target (e.g. CSS selector, URL)
• Action (e.g. click, toBeVisible)
• Category (e.g. Assertion, Timeout)

This structured data enables exploration from multiple angles — similar to using GROUP BY in SQL.

Now, instead of guessing what hides behind Error: expect(locator).toBeVisible() failed you can see that:

• Most tests failed because [data-testid=fg-loader] was not visible
• [data-testid=table-tbody….] visibility is the second most-common failure reason

Explore Playwright Error Explorer documentation.

Custom Test Metrics in Currents

Playwright has evolved beyond testing — it’s now a platform for performance, accessibility, and coverage insights. Our new analytics engine lets you track custom numeric metrics tied to your tests, such as:

• Accessibility score
• Lighthouse web vitals
• Performance metrics
• Resource usage metrics

You can attach numeric metric values to a test (as an annotation) to track it in Currents. See Playwright Custom Test Metrics documentation.

Here’s an example of sending resource usage metrics to Currents:

// Add annotations with a custom metric
test
    .info()
    .annotations.push([
    {
      type: "currents:metric",
      description: JSON.stringify({
        name: "memory_usage",
        value: getMemoryUsage(),
        type: "float",
        unit: "mb",
      })
    }, {
      type: "currents:metric",
      description: JSON.stringify({
        name: "cpu_usage",
        value: getCPUUsage(),
        type: "float",
        unit: "%",
      }),
    }]);

These metrics are automatically processed and surfaced in Currents charts — complete with filtering, aggregation, and trend analysis.

Data Redaction for Trace Files

To strengthen privacy and compliance for our Enterprise Customers, we launched an automatic removal of secrets (tokens, passwords, API keys) from trace files. This feature is available for customers on Enterprise plan.

Benefits:

• Prevents accidental exposure of credentials
• Simplifies GDPR and SOC 2 compliance
• Reduces risk during debugging and collaboration

Read more about Data Redaction.

Improved Jira Integration

A couple of months ago we rolled out our native integration with Jira. The recent release includes a couple of improvements based on customer feedback:

• Create or link an existing Jira Issue when browsing test results
• Show previously linked Jira Issues
• Show Jira Issue details when browsing a test
• Add comment / failure details (with Markdown support) to previously linked issues

See the updated Jira Integration documentation.

Currents MCP Server 2.0

The new analytics platform enabled us to release MCP Server 2.0 released. See the Currents MCP Server documentation.

You can now ask your agent question about your testing suite:

• What were the top flaky tests in the last 30 days — analyze CI test history to identify and resolve flakiness
• What were the slowest specs this week — find the slowest files across recent CI executions

Moreover, you can use AI Agents + Currents MCP server to perform intelligent tasks

• Fix all my flaky tests — investigate patterns in your CI pipeline failures, create a plan, and suggest fixes
• Fix this test — pull the last CI test results and suggest fixes

UI Improvements

Beyond the major infrastructure and API updates, we’ve refreshed parts of the dashboard UI — addressing many of the annoyances reported by our users.

We’re deeply grateful for everyone who shares feedback, challenges, and ideas. Your input directly shapes Currents’ roadmap — and the next wave of features is already underway.

We’ve released MCP 2.0, a major upgrade that makes agents truly autonomous when working with your Currents data.

Previously, MCP could only check specific run data if you manually provided an ID, meaning you often had to stop and grab info from the dashboard. It also had no access to historical data. With MCP 2.0, that friction is gone. Agents can now discover, analyze, and debug your CI test runs on their own.

What’s New

• Seven new tools for exploring projects CI test runs, specs, and results.
• Smarter workflows like finding flaky or slow tests, without needing run IDs.
• Simplified responses and a cleaner, more modular codebase under the hood.

New Abilities for Agents

With MCP 2.0, you can now ask your agent things like:

• 🔍 “Fix this test” → pull the last CI test results and suggest fixes.
• 🐞 “What were the top flaky tests in the last 30 days?” → analyze CI test history to identify and resolve flakiness.
• ⚡“What were the slowest specs this week?” → find the slowest files across recent CI executions.
• 🧪 “Fix all my flaky tests” → investigate patterns in your CI pipeline, create a plan, and suggest fixes.

In short, MCP 2.0 makes your AI agent behave more like a senior engineer with direct access to your test suite, diagnosing issues, spotting patterns, and guiding you to faster fixes.

We’re just getting started with MCP. Your feedback will help us shape where it goes next, and we’re excited to keep making it smarter, faster, and more helpful with every release.

We’re excited to launch our new Jira Cloud Integration, designed to bridge the gap between test insights and issue tracking.

• Create Jira issues directly from test failures in Currents
• Link existing issues and add comments with one click
• Include test context automatically: error messages, stack traces and links
• Autocomplete support for issue search (up to 50 results)
• Supports multiple Jira installations
• Rich formatting with Markdown
• This integration is available now for all customers.

With this update, teams using Currents and Jira can now easily trace failed tests by creating or linking Jira issues directly from the test execution view. No more switching tabs, manually copying logs, or losing context — everything happens where the failure is already visible.

Once enabled, a Jira icon will appear on every test execution page.

Clicking it opens a lightweight dialog that allows engineers to create new Jira tickets or comment on existing ones with rich test metadata (like stack traces, titles, durations, and links to the full run).

The integration is built for speed and minimal friction, with support for multiple Jira installations, project and issue type selectors, and auto-filled context to reduce redundant typing. It’s a simple but powerful step toward tighter alignment between engineering and quality.

• Documentation
• App listing: Currents for Jira

P.S.

Give us a ⭐️!

Currents Actions Engine now supports two new features:

• applying an action based on the error message
• dynamically adding tags using the new Add Tag action.

Requires @currents/playwright@1.15.0

Why it is useful

• Conditionally apply action based on Error Message

  Conditionally quarantine tests if error message (e.g. Error: net::ERR_CONNECTION_RESET) matches a pattern.

• Automate your triage process

  Automatically tag tests that fail with specific error patterns — like timeouts, network errors, or assertion mismatches.

• Create focused reports

  Filter and analyze test recordings by tag. This helps you understand how often a certain error occurs, where it’s happening, and how it’s trending over time.

• No code changes needed

  Tags are applied via the action engine based on matching rules, so you don’t need to modify your tests or test runner config.

We've made a few upgrades to the Currents Integrations

• Revamped the Integrations screen layout to make room for upcoming additions
• Added a Label field to help you distinguish between multiple integration items with the same destination
• Improved handling of misconfigured GitHub and GitLab integrations for smoother troubleshooting

More enhancements coming soon!

Error Explorer highlights the errors impacting your CI executions, making it easier to identify patterns and root causes.

The new, improved Error Explorer view introduces the following improvements:

Error Distribution Timeline

The Errors Explorer displays a timeline chart showing the daily distribution of error messages over the selected period. You can switch the metric and adjust how many top errors to display. Top errors are ranked by their total value for the selected metric across the period.

Error Metrics

• Occurrences - how often an error has caused a failure or a flaky behaviour during the selected period, based on the active filters. This metric counts all occurrences — including repeated ones from the same test. For example, if the error message TimeoutError: Navigation timeout of 30000 ms exceeded occurred 5 times in test A and 10 more times across other tests, the total count will be 15.
• Affected Tests - how many unique tests were impacted by this error during the selected period. Each test is counted once, even if the error occurred multiple times in it. For example, if the same error appears 5 times in one test and 3 times in another, the Affected Tests count will be 2.
• Affected Branches - how many unique branches encountered this error during the selected period. Each branch is counted once, even if the error occurred multiple times on it. For example, if the error shows up 10 times on main and 3 times on feature/login, the Affected Branches count will be 2.

Individual Error Message Details

Clicking an error item reveals more details about that specific error

• Affected Tests – A list of tests impacted by the error, sorted by how often it occurred. These are tests that failed or flaked due to this error. Click a test title to view its details in the Test Explorer.
• Recent Executions – A chronological list of the most recent test runs affected by this error. Clicking on a test title reveal its details in the Test Explorer, clicking on the commit message opens the specific execution details.
• Affected Branches – A list of branches where this error occurred, sorted by occurrence count.

@currents/playwright@1.13.0 focused on improving the efficiency of Playwright Orchestration. While testing the beta version of this feature one of our customers reported a decrease of Playwright CI tests from 42 to 29 minutes (~30% improvement).

The improvement was achieved by a more efficient use of Playwright Worker Processes + a highly concurrent nature of playwright test runner.

If you are already using orchestration, give it a try:

• @currents/playwright@1.13.0 introduces a new configuration option orchestration.batchSize
• set orchestration.batchSize to the number of workers defined in playwright.config.ts
• when orchestration.batchSize is set, in addition to an optimized spit of test files between the CI machines, the orchestration takes into account the # of workers in each machine

See an Example GitHub Repository.

Additional resources:

• Playwright Parallelization techniques overview
• Orchestration Setup instructions

We are happy to announce the release of a dedicated reporter for Node.js Testing Framework.

You can run the Node.js tests, use the dedicated reporter and send the test results to Currents. See Documentation for more details.

Example setup

npm install @currents/node-test-reporter @currents/cmd --save-dev

node --test --test-reporter=@currents/node-test-reporter --test-reporter-destination=./report.xml **.test.mjs

npx currents convert --input-format=junit --input-file=./report.xml --framework=node

npx currents upload --key=XXX --project-id=YYY

Run example

The Test Explorer just got a serious upgrade to help you spot troublemaker tests faster:

• New tabular layout – A more compact, ergonomic table view with sortable columns makes scanning and comparing test data a breeze.
• Group filter – Quickly slice your test list by group to narrow your focus.
• Export results – Need to share results or dig deeper offline? You can now export the table with a single click.
• Volume metrics – We’ve introduced Flakiness Volume, Failure Volume, and Duration Volume to help you identify the biggest contributors to CI noise—even if their raw failure rates are low. Read more.
• UI quality-of-life upgrades – Subtle but meaningful improvements across the board: better spacing, inline actions and flexible layout.

It’s cleaner, faster, and more actionable. Dive in and explore.

Improvements

• Improved support of running only previously last failed tests for runs created with Currents Orchestration

Bug Fixes

• Improve the error message formatting for failed network requests

We've released a new REST API endpoint for retrieving Test Results.

GET v1/test-results/:signature

Using this endpoint you can get… the test results 🤠, filtered by tags, branches or test status, including details like:

• individual attempts details
• duration and timings
• error details
• flakiness indicator
• metadata like git information, project etc.

Check out the documentation for details.

includes Operator for Currents Actions

We’ve added a few additional Currents Actions operators to unlock more expressive configurations. The new operators allow evaluating lists (e.g. test tags or test title path).

For example, for the following expression <subject> <operator> <input>

• includes - all of the input list values can be found in <subject> list
• includes some - at least one of input list values can be found in <subject> list
• missing - all of the <input> values are missing from the <subject> list
• missing any - any of the <input> values are missing from the <subject> list

Requires @currents/playwright@1.10.0

Annotation Filters for Test Results Chart

Playwright Annotations is a convenient way to augment your test results with metadata like Test Owners, Custom Notifications and more.

Now you can refine the Test Results and Test Flakiness charts using annotation typeand annotation description values.

Github

We’ve improved our integration with GitHub and Slack — now you can receive a single message for all groups in a run.

Click on “Single notification for all groups” under the GitHub integration in Project Settings > Integrations > Github to enable it. Read more.

Slack

Click on “Single notification for all groups” under the Slack integration in Project Settings > Integrations > Slack to enable it. Read more.

We’ve improved our integration with GitHub - now you can connect your Currents account to multiple GitHub organizations.

Select the GitHub organization and repository in Project Settings > Integrations to enable GitHub comments, status checks. Read more.

Currents Dashboard

• Improved notifications

  • We’ve revamped the internal implementation of the notifications and integrations system to support an increasing demand for more scenarios
  • A new option was added to Slack and GitHub integration settings to allow sending a single notification for multi-group runs (Slack, GitHub, GitLab)

• Allow setting repository default branch - in preparation for future improvements and to allow tracking trends use the most recent data from the default branch as a reference.

• We’ve switched selected customers to a secure Cloudflare R2 storage and have done the necessary work to allow bringing your own storage for improved security.

@currents/playwright v1.9.3

• Allow using currents.config.ts config file instead of providing CLI arguments or reporter configuration
• Limit the number of nested sibling steps to 2000

@currents/cmd v1.6.8

• Improved support and documentation for Jest, Vitest and NodeJS Test Runner results

We’ve been working on allowing a more granular control of the test results by adding more filters. The recent release allows filtering data in various views by group name.

For example, if you have different tests for different Playwright projects, you can filter the metrics by project name (groups).

We are planning to add more controls and filters like annotations, framework versions, OS etc.

📝 Introducing Run Notes: A new way to collaborate in Currents. Use notes to document failures, flag issues, or share insights with your team.

• Notes are visible to all users, just below the run title.

• Adding, editing, or removing notes is exclusive to admins.

Writing and running tests is just one step in a more comprehensive workflow. With the recent launch of the Currents Actions Engine, we are enabling teams to automate their testing-related workflows.

Currents Actions, combined with detailed reporting, integrations with third-party tools, test result histories, and observability metrics, unlocks these scenarios using a flexible set of rules and actions. It replaces ad-hoc in-house solutions with a single platform accessible to the entire team.

For example:

• Conditionally and temporarily skip or quarantine a test.
• Dynamically add a tag.
• Send an alert or open a ticket if a test becomes flaky.
• Intelligent selection of tests for CI runs: only high-impact tests run on each commit, while nightly jobs run the full test suite.

We are planning to extend the capabilities of the Actions Engine to implement more actions that support best practices of the testing workflows.

Currents has flagship integrations for various testing frameworks via the dedicated reporters (like Playwright, Jest and Cypress).

The recent release unlocks more integrations with other testing frameworks without a dedicated reporter.

We have implemented a set of tools that support JUnit XML (or compatible) reporting format.@currents/cmd CLI utilities allow converting JUnit XML files to a format compatible with Currnets. For example:

• run currents convert to convert test results
• run currents upload to send the results to Currents

This approach unlocks supporting the following frameworks.

• Postman
• Vitest (example TBD)
• NodeJS Test Runner (example TBD)
• WebdriverIO (example TBD)
• Bun (example TBD)
• Cypress 😆 (example TBD)

More details are in the documentation.

The recent release introduces Code Coverage for Playwright. Follow the guide to explore different ways of instrumenting the code and automating collection of the reports using Playwright fixtures.

As your test suite grows and you start running tests in CI (often in parallel) you need to start maintaining the merging of coverage reports from multiple containers or shards, identifying changes in coverage metrics and tracing changes.

Currents simplifies this process by:

• Collecting coverage reports on-the-fly from distributed CI machines
• Handling test retries and interrupted runs accurately
• Uploading raw coverage reports for processing in the background
• Tracking coverage metrics over time, with support for filtering by tags, git metadata, and more

Revamped Coverage Charts

We have refactored coverage charts for more convenient use.

Coverage information at the run level

Additionally, we added coverage details in run summary view. Future releases will highlight decrease in coverage values and would allow proactive tracking and reporting related to code coverage.

We’ve rolled out new plans that include self-served seats customization. Adding more seats to a plan doesn’t require switching to a different tier.

• Add or remove an package of extra 10 seats in the Billing and Usage section
• No need to switch to a different tier to add more seats (up to 30 seats)
• Available for new plans purchased after October 17 2024
• Doesn’t affect already existing subscriptions with customized number of seats

You can attach arbitrary files and content directly to your Playwright tests, making it easier to capture relevant data for review and improved collaboration with your team. With the recent update to Currents you can browse and download arbitrary test attachments.

The attachments will be securely uploaded and stored in Currents cloud storage.

• Requires @currents/playwright 1.6.0+
• No extra charge and no limit on volume
• Subject to your plan’s retention policy

This change unlocks further improvements to Currents platforms that are based on parsing attachments associated with the tests. A few examples:

• Markdown file for test documentation and notes
• Lighthouse reports to track accessibility and web vitals
• Mermaid for charts and diagrams

How to Attach Files to Playwright Tests

Use the following syntax to add attachments to your test:

test('example test with attachment', async ({ page }, testInfo) => {
  // Your test steps
  // ..
  // Attach an MD file
  await testInfo.attach("mdFile", {
    path: "./files/test.md",
  });
});

If you want to embed custom content directly, use:

test('example test with custom content', async ({ page }, testInfo) => {
  // Your test steps
  // Attach custom content
  const logContent = 'Example log content';
  await testInfo.attach('log', {
    body: Buffer.from(logContent),
    contentType: 'text/plain',
  });
});

• Configuration file. Create currents.config.ts|js to define Currents configuration (in addition to CLI flags, reporter configuration or environment variables). Currents evaluates the contents - i.e. you can use custom code and logic within the file.
• Lifecycle functions. Use the configuration file to define custom lifecycle functions. For example, orchestration.onFinish runs after run completion, the function accepts the latest known status of a distributed orchestrated run (reported by the server from all CI machines). You can invoke custom logic based on the reported run progress status - e.g. send an API call or finalize Visual Testing tools run (ArgosCI, Applitools) after all results were reported.

Improvements

• Inline Test Record Links. Console output includes inline links to individual test recordings for more convenient navigation.

Misc

• Report the original run details when rerunning previously failed tests.
• Better support for uploading generic and arbitrary artifacts - that unlocks support for Playwright Coverage and Lighthouse reports.
• Retry failed network requests. We’ve worked with AWS support to reduce the impact of requests failing because of internal AWS issues (the current failure rate is at 0.002%, which is below AWS formal SLA).
• Security patches and minor bug fixes.

Re-running only failed Playwright tests in CI is one of the most popular requests.

Starting from version 1.44 Playwright supports running only the failed test from the last run using CLI flag --last-failed. However, simply adding the flag to a CI command isn’t sufficient when running the tests in parallel using shards or Playwright Orchestration. 😕

Setting up re-runs requires maintaining non-trivial configuration and custom scripts 👎.

That's why we have created a set of tools that unlock re-running only the failed Playwright tests in the most popular CI providers - GitHub Actions and GitLab CI/CD 👍.

🔄 Check out our guide and examples.

We’re gradually rolling out official support for the Jestframework.

You can check it out at Manage Project > Setup Instructions.

We’ve also updated our documentationto include a Jest getting started guide.

Stay tuned as we roll out more features and bugfixes for Jest support 😎

Playwright has a built-in ability to perform a Visual Comparison.

test('example test', async ({ page }) => { 
  await page.goto('https://playwright.dev'); 
  await expect(page).toHaveScreenshot({ maxDiffPixels: 100 });}
);

Playwright will fail a test if the current snapshot differs from a reference image.

We’ve released a first-class support for displaying the visual comparison screenshots, including browsing the diff, actual, expected, side by side and slider widget.

The support is automatic and doesn’t require any action other than just using toHaveScreenshotdirective.

We are happy to announce that we’ve enhanced our SSO integration to support automated users provisioning using SCIM protocol.

Check out the documentation to discover how to enable SCIM.

Improved History Browser

The new history browser allows more convenient navigation and exploration of historical items

Inline browsing for Test Explorer

Test Explorer view allows exploring test performance trends, past executions and most common errors. In past, exploring past executions required navigating to a different view, causing confusion and context switch.

With the recent change the executions are shown inline for more convenient and speedy exploration.

Better navigation for multi-group runs

We’ve improved the layout and filtering options for runs with multiple groups. The new variant allows more intuitive filtering of groups when browsing Spec Files view and Live View.

Inline links to Explorer, Run and Live View

When browsing spec or test results we’ve added a shortcut links for more convenient navigation

• A link to Spec or Test Explorer for the associated entities
• A link to the associated Run View
• A link to the associated Live View (Playwright and Jest only)

Misc

• An improved list items layout to better support long names and inline actions
• Added list line item numbers
• Split complex views into sub-views accessible via tabs
• Better axis labels that auto-adjust to timeline duration

As a follow up on our previous release that included support for Test Annotations - a test owner will be notified via a Slack notification when their tests fail.

To activate the notifications, make sure to enable Slack integration and set owner field value to match Slack username.

See the documentation for more details.

📝 Test Annotations

Playwright Test Annotations allows augmenting test results with additional metadata, for example: a Jira ticket number or Test Rail tracking id.

Starting from version @currents/playwright@1.5.0 , Currents will store test annotations for the recorded tests, the annotations will show up in the dashboard.

Use case - test owners

Some test annotations have a special purpose, for example:

testInfo.annotations.push({ 
  "type": "owner",
  "description": "johnSmith"
})

CopyCopied!

Using type:owner has a special meaning in the dashboard - it will designate… a test owner. Test owner can be a person or a team.

We are working on incorporating the concept into our integrations and across the dashboard - e.g. sending notifications to a person or a team when their test fails, allowing filtering tests by their owner.

Let us know if you have more use cases that involve annotations.

👟 Inline Steps View

One of the unique features of Currents reporter for Playwright is how we upload the results. Instead of waiting for the whole test or a spec file to complete, we stream step-level information. That allows to capture very detailed information - even if playwright or CI machine crashes, we still send and present the last reported step.

The recent release exposes step-level information within test details view for more convenient and effective troubleshooting.

For example, one of our clients uses test steps as a “documentation” - they give steps descriptive names, so team members can quickly understand what’s happening in a test just by glancing at the reported steps.

🌼 UI changes

We revamped the UI for more convenient browsing:

• split test attempt details into tabs (error details, screenshots, videos, traces, steps)
• improved the onboarding and setup instructions to help new users start using the platform

New

Playwright Test Annotations allows augmenting test results with additional metadata, for example: a Jira ticket number or Test Rail tracking id. Starting from version 1.5.0 Currents will store test annotations for the recorded tests, the annotations will show up in the dashboard.

Use case: test owners
Some test annotations have a special purpose, for example:

 testInfo.annotations.push({ 
    "type": "owner",
    "description": "johnSmith"
 })

Using type:owner has a special meaning in the dashboard - it will designate… a test owner. Test owner can be a person or a team.

We are working on incorporating the concept into our integrations and across the dashboard - e.g. sending notifications to a person or a team when their test fails, allowing filtering tests by their owner.

Let us know if you have more use cases that involve annotations.

Fixes

• Retry reporting results when certain network requests fail

• Better support for the Fail Fast strategy, which allows you to automatically interrupt CI runs after a certain number of test failures. You can configure this in Project Settings or via the CLI using --pwc-cancel-after-failures <number | false>.

This is a minor release that fixes a few bugs and mostly contains backend changes to support upcoming features

• Fix: use consistent representation of git commit sha (8 first characters)
• Fix: correctly select machine when machine has tests from multiple groups
• Fix: sanitize and store test annotations, in preparation for using annotations for test owners and notification rules
• Fix: fetch up to 198 nested steps for playwright live view

Customize the metric for runs duration chart: average, P99, P95, P50, Max and Min.

• All the metrics are also available when you export CSV or JSON
• All the metrics appear in the breakdown table
• The selected metric will be used for the calculating the trend line

This release is packed with improvements and bug fixes. See below👇

💅🏻 Run Summary UI

Machines view visualizes the allocation of projects (groups) and spec files on CI machines, using a single SVG pane with a unified timeline.

Selecting a particular machine shows the spec files that ran on the selected machine and execution details:

• Spin-up time (1) - time it took the machine to start reporting results
• Active time (2) - time it took the machine to run its specs

Pin and unpin spec files for more convenient triaging.

🐞 Top run errors

Run Errors tab show failed and flaky tests grouped by error message. Failure and test details show up inline, so you can troubleshoot issues without extra navigation steps.

✨ Similar Errors Detection

When browsing failed or flaky tests, we show a warning if we find that the test failed because of a similar reason on other branches and runs.

🎁 Misc

• You can export data from the dashboard JSON format, in addition to already supported CSV
• Customize Run title for run created via GitHub Pull Request in project settings - use commit message or PR title
• Supporting up to 98 nested steps in Live Results
• Opening a deleted run shows user-friendly error message
• Currents will updating GitHub comment for a successful run with new data even if Failed Only setting is enabled

Leave us a feedback and share your opinion in the comment section below.

Enhanced Command Line Reporting!

With the latest update, you can now utilize Playwright's --reporter flag directly with our command line interface.

npx pwc --key [record-key] --project-id [id] --ci-build-id [build-id] --reporter junit

When utilizing the command line clients, pwc or pwc-p, the default @currents/playwright reporter is automatically enabled. This latest enhancement allows users to incorporate additional reporters alongside the default. Now reporters provided with the --reporter flag will be combined with @currents/playwright and passed along to Playwright.

Special Consideration for Orchestration:

For Orchestration using pwc-p, it's important to note that the reporter executes once for each spec file. Consequently, additional configuration may be necessary to ensure compatibility and support for multiple outputs. Playwright offers the specialized Blob Reporter for merging multiple outputs into a unified report.

Read more

Improvement

• You can now search for errors by "error message" in the Errors Explorer
• Webhooks now include a x-timestamp header

What if you could run E2E tests on spot instances?

• Spot Instances can reduce CI costs by up to 90% 🤩
• However, spot instances can be terminated at any time, which can cause the loss of the test results 😞

Currents Orchestration for Playwright automatically reassigns the tests from to-be-terminated spot instances to another CI machine.

How it works?

@currents/playwright@1.3.0 introduces a new flag --pwc-reset-signal SIGUSR1|SIGUSR2.

After receiving an eviction / termination notifications from your cloud provider, you can send the POSIX signal to pwc-p process to reassign the affected tests to a different machine.

• ✅ no need to rerun the whole testing suite
• ✅ no loss of tests results
• ✅ enjoy the reduced cost of spot instances
• ✅ can be used for other scenarios - e.g. move tests to a different machine based on any event / condition.

Read more

@✨ Playwright Reporter v1.0.0 enabled us to collect as much information as possible as soon as it is available for more efficient troubleshooting of failed CI executions.

Today we are launching a new "Live Results" tab. Here's what you can find in the new tab:

• near-realtime streaming of step-level progress from CI machines (10-15 seconds delay)

• browsing individual step details - including timing, stdout, stderr and error details
• lifecycle timing and breakdown - visualize test lifecycle stages like before all, before each, test body, after each, after all and identify performance bottlenecks

• lightweight alternative to Playwright traces - even if machine crashes or trace generation / upload isn't successful, you can still explore the step-level details reported to Currents

There're improvements planned in future releases, e.g. integrating with other dashboard components (screenshots, artifacts, history etc).

Meanwhile, please let us know what you think! 🤓

Version 1.2.0 of our integration with Playwright includes:

• better compatibility with pnpm due to simplified internal dependencies
• get access to run details and summary, including the link to Run URL and links to recorded test results
  • generate a JSON file with summary of a run:

    --pwc-output-file /path/to/file
    

    CopyCopied!
  • TypeScript type definitions of the summary is available:

    import { ExecutionJSONSummary } from '@currents/playwright'
    

    CopyCopied!
  • 👉🏻 Documentation

We've released an improved Runs Summary view that includes:

• Test results overview, progress and outcome chart with clickable metrics for better navigation

• Group-level progress and results items

• Run and group-level progress tracking

Delete the unwanted runs and never see them again, including in reports and the runs list.

• Open the run you want to delete

• Click "Advanced" tab

• Click "Delete"

• The run is gone!

Spot the general direction or trend of your testing metrics at a glance. Linear trendline helps to see the ...trend of the selected metric while Moving Average smoothes the fluctuations

1. Click the small ⚙️ icon next to the "Trendline" label
2. Select the metric of your interest
3. Set the trendline type: Linear or Moving Average

A new revamped results summary allows more convenient browsing of execution results:

• Cross-run results at a glance, including flakiness rate
• Clickable for more convenient access to test results
• Brower individual group results
• Click on a group to narrow down browsing the results to a specific group

We are excited to introduce v1.0.0 of Currents integration with Playwright 🎉!

npm i @currents/playwright@latest

It includes:

• 🏎️ Fully parallel mode support - set fullyParallel to true
• 🚀 Orchestration for Playwright - better than the native sharding, up to 40% faster CI Playwright runs

👉🏻 Read more

• Better screenshot navigation when browsing test details [CSR-986]

• Added Y axis for projects summary view [CSR-985]

• Added instructions for setting git information [CSR-985]

• Pull Request detection for CI runs executed via GitHub Actions

• Requires @currents/playwright@0.12.0 or cypress-cloud@1.10.0
  • 📚 Documentation

• Released @currents/playwright version 0.11.3:
  • Added --pwc-debug=true|remote|full flag for uploading debug logs to Currents servers for more efficient troubleshooting. Read more.

Improvement

• Released @currents/playwright version 0.11.0:
  • Force non-zero exit status when failed tests are detected during Playwright execution.
  • Added --pwc-cancel-after-failures flag and configuration options to allow overriding fail-fast policy. Read more [CSR-947].
  • Added --pwc-disable-title-tags to disable parsing tags in test titles. Read more.

Fix

• Preserve logical condition operator AND or OR when navigating from insight charts [CSR-914].

Improvement

• Published Playwright Test Status Guide.
• Released @currents/playwright@0.10.8. See the Changelog.
• Refactored side navigation menu based on customers' feedback.
• Compiled and published non-blocking versions of Cypress binaries for versions 9.x.x - 12.x.x.
• Released Docker images that have pre-compiled non-blocking Cypress binaries.

Fix

• Fix handling serial mode Playwright tests: properly detect flakiness and status. Requires @currents/playwright@0.10.8 [CSR-922]
• Fix updating Playwright Tags for projects that have interdependencies. [CSR-931]

• Playwright Tags. We've released Tags for Playwright executions available from version 0.10.0+ on the @currents/playwright package. The feature offers Test Title Tags, Test Group Tags, Tags with--grep, as well as Run level Tags and Project Level Tags [CSR-133].
• Filter in insights by projects from Playwright. With the Playwright tags, this request is also met through Project Level Tags [CSR-893].
• Exclude tags from Playwright test names. With the Playwright tags, this request is also met. You can find more details here[CSR-845].

New

• Spec files API. Now you can use the new API resource for fetching the spec files from a project via http request. You can use filtering and sorting according to our API documentation [CSR-840].

Improvement

• Playwright run cancellation. We’ve released the support for cancelling Playwright runs. Previously you wasn’t able to do it but now you can do it via API or Currents dashboard [CSR-612].

Fix

• Cancelled tests status. Previously, the cancelled runs were always failed. Now the cancelled runs are getting the tests status so you don’t get distorted analytics [CSR-751].

Improvement

• Improve flakiness rate visualization in the Test Flakiness graph (Analytics). Now, the Test Flakiness graph presents a more readable scale for small flakiness rates. The graph shows the number of flake tests on the left side of the graph and the flakiness rate on the right side [CSR-771].

• Filter by group in the Spec Files Tab [CSR-694].

• See Tags on the Compact Runs View [CSR-697].

Fix

• Prevent invalid billing emails through a validation mechanism before saving them on Billing & Usage [CSR-773].

New

• Coverage UI. We've launched Coverage reports collection in beta mode, which provides information on whether and how frequently certain parts of code have been executed. It's available for Cypress tests. Code Coverage for Playwright will be out soon!
• Archiving Projects on Currents Dashboard. Now you can archive and unarchive projects listed on your organization's main page [CSR-703].

  

Fix

• Fix a bug reported on Github where responses of network requests were not able to be tracked, showing as [content] [CSR-811].

Test Explorer Filters. Persist filters when diving into tests. The filters are now persisting on the new page, and there is no need to filter again [CSR-701].

Top flaky errors. We released a new section showing the top errors causing test flakiness. Those are the most frequent errors collected from the failed attempts of flaky tests. The view is available in the Tests Explorer section and also when browsing individual test results [CSR-668].

Customizable default Projects Summary view. Now you can set the lookback time period and filters (tags, branches and authors) for each individual project [CSR-668].

• Pin branches for more effective navigation of Test Executions History. Click the currently displayed branches or type a custom name to freeze the branch while navigating the executions history [CSR-95].

Improvement

• Single-Sign-On added a dedicated link to sign into the dashboard using the pre-configured SSO provider and skipping the login form [CSR-716]
• Updating SSO documentation link added onto the Dashboard [CSR-708]
• Gitlab Integration: bring more information onto the run summary - build ID, who triggered the commit, as well as date and time stamp [CSR-620]

• Automated reports: make the way to add emails more intuitive by adding badges when the user inputs tags, authors, and branches [CSR-625]

Fix

• Fix a bug where expiring sessions did not preserve URLs. Now it redirects users to the last known URL after logging out due to an expired session [CSR-652]
• Fix a bug that caused login sessions to expire prematurely

Improvement

• Billing & Usage section now displays the usage data aggregated by usage cycle, instead of by calendar months. That should provide more accurate information about the recorded usage.

• Billing & Usage section allows navigating between usage cycles.

• Usage aggregation changed from daily to hourly. Aggregating usage hourly (instead of daily) allows more precise reporting and calculation of extra recorded tests
• Customers can opt into an extra usage plan via the dashboard without contacting support or requesting to increase the limits temporarily.

Fix

• Tags for multi-group runs: only tags from the initial run were applied for multi-groups runs. Now the runs have all the tags from all the groups [CSR-645].
• Edit the order of the Projects: project graphs on the main page were moving slightly while in edit mode [CSR-650].

New

• Automatically Cancel runs via GitHub Actions [CSR-75]

Improvement

• Support multiple Playwright videos [CSR-538]
• Multi-step ordering for runs with failure-based strategy [CSR-579]
  • First, sort by the failure rate
  • Second, sort by the expected duration
  • Third, sort by alphanumeric spec name
• Add a small copy button near the commit sha [CSR-617]

Fix

• Insights - Run Status - Fix an issue that sometimes marked cancelled runs as passed [CSR-630]

Improvement

• Specify config files using --cloud-config-file CLI option [CSR-634]
• Support --headed CLI flag [CSR-567]
• Faster reporting using spec:before hook [CSR-3]

Fix

• Identify and report cypress crashes [CSR-3]
• Support ESM projects [CSR-635]

GitHub Release

• https://github.com/currents-dev/cypress-cloud/releases/tag/v1.8.0

Improvement

• [CSR-624] Executions history browser improvement
  • Highlight the current item.
  • Prevent race condition when navigating between execution history items.

• Show groups identifier for spec file summary when run contains multiple groups

• Change the state of specs with no tests or with all tests ignored as "no tests"

Fix

• [CSR-563] Fix corrupted links in the breadcrumb navigation - support native browser navigation

Improvement

• [CSR-558] Machines and workers visualization for Playwright runs. The visualization shows the distribution of spec files between machines (shards), and individual workers on each machine. Requires @currents/playwright@0.6.1+

• Machines visualization marks specs files with flaky tests as a striped bar:

• Automated Weekly report improvements:
  • Show the previous week's metrics, including the change indicator for Summary and Runs Performance:

• Trends section now shows the previous week's metric, the current week metrics and the difference:

• The report template styling was refactored to have more spacing and better fonts 💅🏻

Fix

• [CSR-611] Fix a race condition that prevents proper status checks and comments posting to 3rd party integration.
• [CSR-212] Automated Reports fixes - remove trends with negative change, do not show items with no recorded executions in the report.

Improvement

• [CSR-3] cypress-cloud@1.8.0-beta.2 with improved support for cypress runner crashes and faster reporting via cypress spec:before
• [CSR-254] Show more characters (32) for group name badges

Fix

• [CSR-549] Bugfix - limit Slack messages payload to lt 3000 characters to prevent response 400
• [CSR-547] Bugfix - show the correct framework (Cypress or Playwright) for Slack, GitHub and GitLab notifications
• [CSR-132] Fix machines view for specs with no tests or when duration is 0ms
• Mark a spec file as failed when an exception is detected while trying to run cypress

New

• Override fail-fast settings via CLI: Override fail-fast settings via CLI flag --auto-cancel-after-failures. Read More. Available in cypress-cloud@1.7.0
• Skip Cloud Orchestration: Run cypress-cloud in offline mode, skipping the orchestration by setting --record false. Available in cypress-cloud@1.7.0

Improvement

• NX Integration: A new version of @currents/nx plugin was released. It is compatible with Cypress 12.7.0+ and uses cypress-cloud package behind the scenes. https://github.com/currents-dev/currents-nx
• Replace images with emojis for GitHub Comments - a cleaner layout and fewer characters allow embedding and sharing the message.

• Sort Specs by execution order

New

• ✨ Automated Reports help teams to proactively identify regressions in test performance and take an action

  

  • Prevent problems that go unnoticed for weeks
  • Reduce the waste of CI resources caused by failed or flaky tests
  • Avoid your team's frustration from rerunning unreliable and flaky tests again and again Read more

• Clickable Test Flakiness and Results charts

Clicking on a bar in Tests Flakiness / Results insights view would open the list of the flakiest or most failing tests for the selected period.

• Reversed order of Insight Charts data table

The latest entries would appear first

• Improved cypress-cloud batched parallelization.

The default duration-based load balancing prioritizes the specs with the longest expected duration. When the longest spec files appear in the same batched together, the overall duration can increase. The improved orchestration prevents this. This is only applicable to cypress-cloudintegration.

• Limit login methods for SSO-enabled organizations

• Copy the contents of a code block

• Clickable Insights Chart Bars - clicking on a chart bar would open the runs created within the timeframe.

  

• Slack notifications - show the failed spec files and tests summary.

The Date Selection component was updated:

• Added "Today" to the predefined dates list
• Added a hint setting a custom data range

  

Fix

• Improve performance by loading Run Summary errors list on demand
• Backend performance improvements to improve the loading speed for runs with many spec files

Identify and troubleshoot the most common errors detected across multiple runs.

The errors are sorted according to the # of occurrences, and you can filter the occurrences to only account for errors detected between specific dates, on specific branches or tags.

Expanding an error item would show additional details:

• tests, branches and tags with the highest # of failures due to the error
• the most recent executions failed due to the selected error

Improvement

More Top Errors in Run Summary

Run Summary shows more Top Error Items (up to 15)

Increase the default images expiration for REST API

The default expiration for signed storage URLs was increased to 3 days for screenshots/videos returned as part of the REST API responses

Shorter identifiers

We are using shorter entity identifiers to allow more compact URLs

Password-based Login Form

You can now set a feature flag to always show the password form on login screen. The FF is stored in the browser's local storage, so if you use many browsers, you will need to set the FF on each of them.

Visit the following URL to activate the FF: https://app.currents.dev/?enforceLoginWithPassword=1

Fix

• Fixed a bug where existing users that are migrating to SSO would see an empty screen on the first sign-on attempt using the SSO

You can now export Insights as CSV directly from the dashboard. For more comprehensive use cases, you can still use the REST API.

You can now select "AND" or "OR" logical operator when filtering by tag.

We are happy to announce the release of a new parallelization strategy that is based on the expected Failure Rate.

The spec files with the highest expected failure rate will run first and that can provide faster feedback. Together with "Fail-Fast Strategy", it can greatly reduce CI usage.

👉🏻 Read More