This documentation supports the 21.3 version of BMC Helix ITSM: Change Management. To view an earlier version, select the version from the Product version menu.

Testing the release

After a release request is approved at the Test Approval phase, you must test it at the Test milestone before you can release it. Testers can be business staff, users, or other IT staff. Once they verify the release, you can roll it out.

g_rm-test_61582_516.gif

Important

For release coordinators, the Test milestone is mostly a manual stage to verify that the service work is successful in a controlled environment. You must use the Release form to update information, revise your plans, add additional change requests, and activities. In most companies, the Test milestone is interchangeable with the Build milestone.


To test the release

  1. Open the release request at the Test In Progress status.
  2. Revise the start and end dates as needed.
  3. Add changes or activities to the release as needed.
  4. Click Rollup to accumulate the risk level, costs, and time spent from the related change requests (displayed on the Manifest tab).
  5. Save your changes.
  6. Use the Process Status Flow area to move the release request from the Test In Progress status to the Deployment Approval phase.
    The release must be approved before it can move forward. For more information, see Deploying-the-release-to-the-business.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*