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.
When TestingBot sees a
build identifier in the desired capabilities of your test, we will add the test to the group you specified.
In our member dashboard, 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.
red slice of the pie-chart to see a list of
For each build, we calculate an
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.
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.
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.|