---
title: Selenium Builds - Efficiency and analytics
description: Improve the parallel efficiency of your Test Builds with Selenium.
source_url:
  html: https://testingbot.com/support/analytics/builds
  md: https://testingbot.com/support/analytics/builds/index.md
---
# Test Builds

Test Builds are group of tests. This term is usually used in a CI/CD context.   
 Whenever you want to deploy to production, you'll run a group of tests to verify the build.

It is possible to [annotate your Selenium WebDriver tests with a build identifier](https://testingbot.com/support/web-automate/selenium/test-options#build).   
 When TestingBot sees a `build identifier` in the desired capabilities of your test, we will add the test to the group you specified.

## Build Graph

In our [member dashboard](https://testingbot.com/members), navigate to the build overview page and click a build name.   
 You will see a page with a pie-chart of the build's success rate and a table with all tests included in this build.

 ![Build Analytics](https://testingbot.com/assets/support/analytics/build-d16f497f14b60b08e5a47b0ab2b59b4080a905946fd5e95fc52b6131955b812b.png)

Click the `green` or `red` slice of the pie-chart to see a list of `passed` or `failed` tests.

## Build Efficiency

For each build, we calculate an `efficiency percentage`.

This number indicates how well your test runner has been using `parallelization` to shorten the total test duration of the test build.   
 One of the advantages of using TestingBot is its `concurrency`: run multiple tests simultaneously to drastically shorten the total time required to run all your tests.

For example:

- Running 10 tests in the build `sequentially`, where each test takes 30 seconds, would result in a total test build duration of **300 seconds**.

- Running these 10 tests in `parallel`, where each test still takes 30 seconds, would result in a total test build duration of **30 seconds**.

The `efficiency percentage` is calculated as a percentage. It is based on how long the build took to run, compared to the duration of the longest test in the build.

  Efficiency Percentage | Degree of Parallelization | Description || 0%-20% | Sequential | All your tests have been running sequentially. Consider speeding up your build time with parallelization. |
| 20%-90% | Semi-Parallel | Some of your tests are running in parallel. There is still room for improvement: add more parallelization to run all tests in your build simultaneously. |
| 90%-100% | Full Parallel | You are taking full advantage of parallelization and your test build is optimised for the fastest build time. |

Was this page helpful? Yes No 

## Looking for More Help?

Have questions or need more information?   
 You can reach us via the following channels:

- [Email us](https://testingbot.com/contact/new)
- [Join our Slack Channel](https://join.slack.com/t/testingb0t/shared_invite/zt-3bcw9xch-jk19~6XPs_xBrsAgAedkCw)