Once the development team has completed several stories, they can create a build and submit it for testing. The concept of a build falls under the scope of software configuration management. The primary purpose of a build is to define the testing scope, facilitate interaction between testers and developers, and resolve issues related to different build releases and bug fixes.

After submitting a build for testing, a test request is successfully created. Testers then link test cases to the test request and execute them to complete the testing process.

I. Create builds

1. Create a build

After completing stories or resolving bugs, the development team can create tags in their code repositories (such as Gitfox, SVN, Git, or GitLab). The project or execution owner, or the release manager, can create a build by navigating to Project (or Execution) > Build.

图1

When creating a build, if the project or execution is linked to only one product, the product name is displayed directly. If it is linked to multiple products or multiple branches of a single product, you can switch between them using the dropdown list. Applications can be managed in the application list under the product release section.

图2

2. Link stories and bugs

After a build is successfully created, you can use the action buttons to link stories and bugs. The stories and bugs linked to a build define the exact testing scope for the testers.

图3

After clicking the Link Story button, a list of stories unlinked to the execution will appear. Check the desired stories and click the Link Story button to complete the process. You can follow the same steps to link bugs.

图4

Once successfully linked, the stories and bugs will be visible in the build list.

图5

Additional notes:

• Finished stories: Stories that are fully developed and linked to the build.
• Resolved bugs: Bugs that are marked as resolved, where the "resolved build" matches the current build.
• Generated bugs: Active bugs where the "affected build" matches the current build.

3. Edit and delete builds

Managing a build involves editing its basic information or deleting it entirely. You can perform these actions using the Edit and Delete buttons.

图6

You can also click to view detailed information on the build details page.

图7

II. Create integration builds

The primary purpose of an integration build is to package completed stories and resolved bugs from several iterative builds within a project for comprehensive integration testing.

Integration builds are only effective at the project level. When creating a build under a project, you can choose whether it serves as an integration build.

If you select the integration build option, you can link multiple iterative builds into this single comprehensive package.

图8

After selecting multiple included builds, all finished stories, resolved bugs, and generated bugs from those sub-builds will automatically link to the integration build. All other features function identically to a standard single build.

图9

III. Submit for testing

After linking stories and bugs to a build, you can submit it for testing by creating a test request.

图10

Click the Submit Test button in the action column on the right side of the build list. This action redirects you to the test request creation page.

If previous builds within this project or execution have been submitted for testing and generated test reports, those reports will be listed to provide a reference for the current testing cycle.

图11

You can view successfully created test requests by navigating to Project (or Execution) > Test > Test Request. Once the test request is created successfully, you can notify the testers to begin testing.

图12

图13

图14