Managing Builds
Add a new patch instead of creating a new cycle. You can record the execution results for Builds.
The development team delivers a bug fix in a patch. The QA team adds and executes relevant test cases. On the Test Suite Execution screen, the QA Lead assigns a build to these test cases for easy identification.
Adding Builds
To add a new build, perform these steps:
Go to Projects and select Build.
Note
Admin can assign Rights related to Build from Roles.
Add new Builds and edit the details of an existing Build.
To add a new build, click New.
Enter the build name and its relevant description.
Select the associated releases from the drop-down list to link.
Click Create.
The build appears on the Build list on the Test Execution Screen when the test execution is associated with the same releases and cycles.
Editing Builds
To edit a build, perform the following steps:
Go to Projects and select Builds.
Click Edit.
Make the required changes to the details and click Update.
Setting a Build as the Default Build
Note
The Set Default option for default build configuration on the Build Create and Edit screen is available only if you have the Customization package.
Set Default—Yes: The build is set as the default build on the execution screen for the selected Release Cycle combination.
Testers do not need to set the build manually, which also helps reduce build association errors.
QA Manager can always set the current build as a Default Build to ensure the executions are always associated with the current build.
Only one default build can be set for a given combination of a Release Cycle.
Set Default - No: Makes the Build a non-default. When some other build is set to default, this flag is set to “No” for the previously default build.
Edit, Build, and Set it as Default.
On the Edit Build screen, edit existing build data and add new release and cycle with default build value in edit build screen.
While editing an existing build, the Set Default toggle option is available. Turn the toggle ‘On’ to mark the build as default for the Release and Cycle combination.
Mark the build as default either while adding new Releases and Cycles to the build. You can mark the build as default build for multiple combinations of Releases and Cycles at a time.
 |
Mark the build as default after adding new Release and Cycle to the build.
View the Releases and Cycles that are associated with the default build on the Build grid.
On the Execution Screen
When a build is set as default and you change a test case status on the Execution screen, a confirmation message shows the default build. Click Yes to proceed. The Build Name column shows the build used for execution.
To run the test case on another build, click No and change the build using the Set Your Build option.
Archiving Builds
Archive builds that were added by mistake or are no longer needed. Once archived, the build becomes invisible across QMetry, including reports.
Use Case 1. A Tester added a Build by mistake and now they do not want the Build to appear on the screen. So they archive the Build to hide it.
Use Case 2. A Tester has completed working on a particular Build. Now the user does not intend to relate any test case to that Build and work on it. For the reason, they archive the Build.
Go to Projects and select Builds.
Click Archive button for the Build.
To unarchive the archived build, click Unarchive for the build.
Unassociate Release and Cycle
Open the Build Edit page.
Locate the section displaying association of Release and Cycle with Build.
To dissociate release or cycles from a build, click Unassociate