Setting Up the Build Inactivity Time [Build Splitting]

Build Splitting, or Build Inactivity Time, is a feature that allows you to organize tests more efficiently. It allows you to track your progress by identifying tests that are run at specific intervals. You can use the Build Splitting feature to set a time interval after which the system will wait for the defined time and mark the build as completed. Any new builds you run after this time period will be created as a new build.

How it works?

Previously, when you ran a build on LambdaTest, all tests were merged into the same build, making it difficult to identify those tests that were run at specific intervals. As a result, we have introduced Build Splitting logic, which helps you organize your tests better.

Build Splitting logic requires you to set Build Inactivity Time. For instance, if the Build Inactivity Time is set to 5 minutes, the system will wait 5 minutes after the last test is completed before marking the build as complete. Upon completion of the build before the inactivity time, the test will be run in the existing build. However, if you run a test (even with the same name) after the specified inactivity time (i.e., 5 minutes), it will come under the new build.

How to set the Build Inactivity Time?

Note

By default, the build inactivity time is six hours.
Every user within the organization can set their own build inactivity time.

To use the Build Splitting functionality, follow the below steps:

Log in to your LambdaTest account. Don't have an account, sign up for free.
From the top-right corner, click on the Profile avatar, and navigate to Profile > Product Preferences.
Under the Automation Build Preference, select the Build Inactivity Time to choose your preferences.