Feature Overview

After the development team completes a set of requirements or bug fixes, they can create a build and submit it for testing.

Using the concept of a build in software configuration management helps define the scope of testing, improve collaboration between developers and testers, and manage release and bug-fix activities across different builds.

After a build is submitted for testing, a Test Run is created. Testers can then link and execute test cases in the Test Run to complete the testing workflow.

Use Cases

• After the development team completes requirements or fixes bugs, Project Builds help define the scope of testing and make follow-up test work easier to manage.
• Based on the requirements and bugs linked to a build, testers can execute the corresponding test cases and complete testing.
• Project owners or release managers can use builds to manage multiple branches of a product or multiple linked products.
• In integration testing, requirements and bugs from builds across multiple iterations can be packaged together to achieve broader test coverage.

I. Create a Build

1. Create a build

After the development team completes some requirements or resolves some bugs, they can create a tag in the code repository, such as GitFox, SVN, Git, or GitLab.

Project owners, execution owners, or release managers can then create a build in Project/Execution > Builds.

图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 to multiple branches of one product, you can switch between them in the dropdown list.

Apps can be managed in the App List under product releases.

图2

2. Link requirements and bugs

After a build is created successfully, you can use the Link action to associate requirements and bugs with it. The requirements and bugs linked to the build define the testing scope for testers.

图3

After you click Link Requirements, the system lists requirements in the execution that have not yet been linked. Select the requirements you want and click Link Requirements to complete the action. Bugs can be linked in the same way.

图4

After requirements and bugs are linked successfully, they can be viewed in the build list.

图5

Other notes:

• Completed Requirements: Lists requirements that have been fully developed and linked to the build.
• Resolved Bugs: Lists bugs that are in the Resolved status and whose Resolved In Build value is the current build.
• Reported Bugs: Lists bugs that are Active and whose Affected Build value is the current build.

3. Manage builds

Build management includes editing build details and deleting builds. You can use the Edit and Delete actions to do this.

图6

You can also click View Details on the build details page.

图7

II. Create an Integration Build

The main purpose of an Integration Build is to package completed requirements and resolved bugs from builds across several iterations in the same project for integration testing.

Integration Builds are available only at the project level. When creating a build under a project, you can choose whether the build is an Integration Build.

If Integration Build is selected, you can include multiple builds from different iterations.

图8

After multiple builds are selected, their Completed Requirements, Resolved Bugs, and Reported Bugs are automatically linked to the Integration Build. Other functions work the same way as for a standard build.

图9

III. Submit for Testing

After the required requirements and bugs have been linked to a build, you can submit the build for testing and create a Test Run.

图10

Click Submit for Testing on the right side of the build list to open the Test Run creation page.

If previous builds in the same project or execution have already been submitted for testing and completed with generated Test Reports, those reports are listed as reference material for the current round of testing.

图11

The created Test Run can be viewed in Project/Execution > Test > Test Runs.

After the Test Run is created, testers can be notified to start testing.

图12

图13