After the development team has completed several story functions, they can create a build and submit it for test.

In software configuration management, a build primarily serves to clarify the testing scope, facilitate interaction between testers and developers, and manage issues related to the release of different builds and bug fixes. After the build is submitted for test, a test task is successfully created.

Testers link test cases in the test task and execute the test cases to complete the testing.

How do developers create builds and submit for test in Sanplex? Check out the video explanation: 【视频介绍】

I. Creating a Build

1. Creating a Build

After the development team completes some stories or resolves some bugs, they can create tags in the code repository (gitfox, svn, git, GitLab). The project/execution manager or release manager can create a build in Project/Execution > Build.

图1

When creating a build, if the project/execution is linked to only 1 product, the product name is listed directly. If the project/execution is linked to multiple products or multiple branches of a product, you can switch in the dropdown list.

Applications can be managed in the application list under Product Release.

图2

2. Linking Stories and Bugs

After the build is successfully created, you can link stories and bugs through the link action buttons. The stories and bugs linked under the build define the testing scope for the testers.

图3

After clicking Link Story, the unlinked stories of the execution are listed; check the boxes and click the Link Story button to complete the story linking. The same operation can be performed for linking bugs.

图4

After successfully linking stories and bugs, you can view them in the build's list.

图5

Other notes:

• Completed Stories: Stories linked to the build that have finished development.
• Resolved Bugs: Lists resolved bugs whose resolved version is the current build.
• Generated Bugs: Lists active bugs whose affected version is the current build.

3. Maintaining a Build

Maintaining a build includes editing and modifying the basic build information, and deleting the build, which can be operated via the Edit and Delete buttons. **

图6

You can click to view details on the build details page.

图7

II. Creating an Integration Build

The main purpose of an integration build is to package the completed stories and resolved bugs from several iteration builds under a project during integration testing.

Integration builds are only effective under a project. When creating a build under a project, you can choose whether it is an integration build.

If "Integration Build" is selected, the included builds can link multiple builds under iterations.

图8

After selecting multiple included builds, the completed stories, resolved bugs, and generated bugs under the related builds will automatically be linked to the integration build; other functions are the same as a single build.

图9

III. Submitting for Test

After the build is linked with stories and bugs, it can be submitted for test to create a test task.

图10

Click the Submit for Test operation button on the right side of the build list to jump to the create test task page.

If previous builds of the project/execution have been submitted for test and completed testing to generate a test report, the related test reports will be listed to provide a reference for this round of testing.

图11

The successfully created test task can be viewed in the Project/Execution > Test > Test Task list. After the test task is successfully created, you can notify testers to start testing.

图12