QMetry defines a Build as a specific iteration of the product/domain to be tested. The feature allows the tester to assign a "build" (aka patch, drop, or increment) to test suites/test cases that indicates indicate the version of product being tested. It helps users track multiple builds of software more dynamically without having to add separate test suites with every new build.
...
Users will have the following options:
Set Build selection mandatory in the project.
Set a Default Build for a release cycle combination.
Assign Build to the entire test suite.
Assign Build to individual test cases in the test suite.
These points are explained as below.
...
If the default build is set for particular release/cycle then this default build is set automatically at the time of adding the test run. A confirmation message pops up asking whether to continue the execution on the given default build.
Note: Bulk Execution performed on the Bulk Execute screen (Test Suite > Test Execution tab > Bulk Execute) is exempted from the application of default build. All the bulk executions from this screen will be performed on None build.
Create Build and Set it as Default
...
You can mark the build as default either while adding new Release(s) & Cycle(s) to the build. You can mark the build as default build for multiple combinations of Release(s) & Cycle(s) at a time.
...
You can mark the build as default after adding new Release & Cycle to the build.
...
You can view the Release(s) & Cycle(s) that are associated with the default build on the Build grid in Projects > Builds.
...
To execute the test case on other build, click No and change the build using the “Set Your Build” option for that test case.
...
3. Set Build at Test Suite Level
When the customization package is not optedpurchased, it is users can not possible to set a build as default.
When executing test cases, if the tester sets a build, then the test case execution sets the executed build as the selected build.
The last build that was set for the test case always gets set as the executed build, if going forward build is not selected during execution.
When executing test cases, if the tester does not set a build then the test execution sets the execution build as None.
Below are the steps to assign the build to a test suite. Build assigned to a test suite will be applied to all the test cases under that test suite.
Steps
Click on the Set Your Build button at the right corner of the screen.
Open the Select Build drop-down and select the build you want the test cases to be executed against. This list contains all the builds that are linked to release and cycle, which are associated with the test execution that is being carried out.
Build will be assigned to the entire test suite if
All Test Cases are selected while selecting build OR
No Test Cases are selected while setting the build.
...
4. Set Build at Test Case Level
...
Below are the steps to assign build to a test cases.
Click on the Set Your Build button at the right corner of the screen.
You can see that all the test cases are selected by default. Unselect the test cases to which you do not want to apply the build.
Open the Select Build drop-down and select the build you want the selected test cases to be executed against. This list contains all the builds that are linked to release and cycle, which are associated with the test execution that is being carried out.
The Build is set for those test cases that are selected while choosing the build.
...
Current set build (i.e. set default build): The build set as default in the Build module. This is a test suite level build. You can change the build at test suite level and the same is displayed as Current set build until you refresh the execution screen.
Last executed build: The build set for test cases on the execution screen and on which the test case(s) are executed.
...