Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Canceling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
        • Tests Performance
      • Spec Files Explorer
        • Spec Files Performance
      • Errors Explorer
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • Billing Emails
  • Usage Information
  • Extra Usage Plans
  • Legacy Plans

Was this helpful?

  1. Administration

Billing & Usage

Managing Billing and Subscription for your Organization

PreviousTroubleshooting SSONextBilling and Pricing

Last updated 11 months ago

Was this helpful?

The Billing and Usage view is accessible by accessing the org management menu - click on Organization > Billing & Usage. Within the Billing & Usage view, you can explore the organization's usage and plan limits, and manage the subscription and billing email recipients.

Billing Emails

You can add recipients for billing-related notifications:

  • notification about successful payments

  • alerts about non-successful payments

  • invoices and receipts

Please note, that billing notifications are different from operational notifications (by default operations notifications are being sent to all the members with Admin rol)

In order to add additional recipients, navigate to Organization > Billing & Usage. Then add a new email in the Billing Emails section:

Usage Information

The Billing & Usage view displays the Usage section with a daily/monthly breakdown of the recorded tests.

Skipped tests it.skip do not count towards usage for billing purposes

How to estimate your test usage

To estimate your test volume, count all your it statements and multiply by your provider's average number of CI runs.

The usage is aggregated hourly to allow precise reporting and calculation of recorded tests.

Usage Information filters

You can filter usage by period and view all past billing cycles. Moreover, you can filter by tests or runs. Most customer contracts are metered by runs.

Usage per project

If you click Show Usage Details, you can see a breakdown of all recorded tests and runs per project created within your organization account.

Extra Usage Plans

If you are still determining how many tests you need per month or if your usage is seasonal, Currents offers extra usage plans in addition to your test package. These extra usage plans offer customers more flexibility to run tests when needed.

When you reach the test limits, Currents will send you an email notification informing you of the activation of the extra usage plan. You also can see the extra recordings progress on the Usage Information:

At the end of the monthly cycle, the billing will include the additional usage recorded. In the case of annual plans, Currents will send a separate bill with the extra tests.

Legacy Plans

Our legacy plans (created before April 2023) do not have extra usage enabled.

When legacy plan subscribers reach the usage limits, our system automatically increases the quota by 10% to safeguard your usage. Then, you will get emails from our automated system with warnings, asking you to upgrade your subscription or activate an extra usage plan.

You can activate an extra-usage or upgrade the plan in Billing & Usage section:

If upgrading is not an option, you can contact us via support@currents.dev or our in-app support chat to activate an extra usage plan to accommodate your increased usage needs.

Please remember that if you surpass your usage limits, Currents will cease recording tests on your organization dashboard. To avoid service interruption, don't hesitate to contact us to activate an extra usage plan or explore subscription upgrades. We're always here to help!

The usage includes a or test recorded to Currents Dashboard. Retries of the same test are considered a single test result, therefore, a counts as one record, regardless of the number of attempts.

The cost for extra recordings ranges and depends on your plan. For detailed pricing information, please check our . If you have any questions or concerns, please don't hesitate to contact us via support@currents.dev or our in-app support chat.

Failed
Passed
Flaky Test
pricing page
Adding additional recipients for Billing Emails
Example - Usage history chart and filters
Usage per Project
Example - Extra usage activated
Enabling Extra Usage for Legacy Plans