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 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 an individual 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 an entry is counted as a test by checking if Test Observability displays it as a separate line item in the test listing.

Illustrating test execution count with an example

Test Observability bills the total number of non-BrowserStack test executions by multiplying the number of non-BrowserStack 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:

You can see that the total number of non-BrowserStack test executions considered for billing (last column) is calculated by multiplying the number of different types of tests (column D) with the corresponding number of build runs (column E) and adding them up.

Non-BrowserStack test executions

Any test execution run outside the BrowserStack infrastructure is a non-BrowserStack test execution. These include local test executions and test executions run on other cloud service providers. Non-BrowserStack test executions can be of any type like unit tests, regression tests, and API tests.