Test execution count for billing in Test Observability

Learn how Test Observabilty counts tests for billing purposes.

Test Observability uses the number of test executions as the main metric for billing.

For Test Driven Development (TDD), Test Observability counts each it block in Test Driven Development (TDD) as a separate test. Similarly, Test Observability counts each scenario as a separate test in Behavior Driven Development (BDD).

Test Observability also counts hooks that run once for a block of test cases or at a file level (global hooks like beforeAll, and afterAll) as tests for billing purposes.

You can verify if something is counted as a test by checking if Test Observability displays it as a separate line item in the test listing.

Test Observability standalone plan

In the standalone plan with test executions as the value metric, Test Observability calculates the total number of test executions by multiplying the number of tests by the number of times they run across various browser and device combinations.

The following sample table illustrates how the test executions are counted:

Automate - App Automate bundled pricing plan

The bundled plan includes unlimited test executions running on Automate and App Automate.

You can also push other tests that do not run on Automate or App Automate. These tests can include various types, such as unit tests, API tests, and tests run locally or on another cloud infrastructure. The number of such tests you can push to Test Observability in the bundled plan is determined by multiplying 8000 with the total number of parallel executions allowed for Automate and App Automate in your plan.