Testing
In this stage, the processes built for the release are tested for common bugs and functionality issues by the Quality Assurance (QA) team. This is done to check whether the development has met the requirements outlined in the release plan without compromising on the quality standards.
All issues found during the QA testing must be carefully documented to follow up on the resolution. They are prioritized based on their business impact, and the release request is reverted to the development team for the fix.
The QA team approves the release after ensuring that the processes function as expected and moves it to the User Acceptance Testing (UAT) team.
Testing could take many iterations. However, it is important to meet the deadlines set for the release.
To add and view the testing-related details,
- Go to Releases.
- Choose all or a specific customer from the drop-down in the header.
- Go to the details page of the required release.
- Click Testing on the left pane.
You should now see a page displaying the following tabs:
- Details:
- Spot-edit the relevant fields to provide the expected and actual testing time frame.
- Describe the testing process under Description.
- Attach test case files.
- Attach records of the issues found while testing.
- Tasks: Add, edit, organize, delete, pick up, trigger, and close release tasks, assign owners to the unassigned tasks, and configure task dependencies. Learn more.
- Notes: Provide testing-related additional information. You can also add testing notes via conversations.
- Approvals: Define approvers for various approval levels required to complete the testing. Learn more.
- Status Comments: View all testing status comments provided in the release form.
Related Articles
User Acceptance Testing (UAT)
In this stage, stakeholders and end users company-wide test the release processes and give their feedback. This stage is crucial for any product release as users test and validate the release using a large volume of real-time data. It takes a ...UAT
User Acceptance Testing (UAT) is the stage in which some users evaluate the implemented change under real-world scenarios. Based on their experience during the testing period, the UAT members provide their consent on approving the change. Role ...Stage and Status
The progress of each stage in a release life cycle is tracked by specific statuses. You can create and manage stages and statuses for the release under Setup > Customization > Release Management > Stage and Status. Users with Edit Releases permission ...Release roles
The release roles allow you to define access permissions to various stages in releases. You can either customize the default release roles or define new roles as required and associate these roles with users when creating a release. Association of ...Stages and Statuses
Release stage is a directional classification that indicates a significant event or a milestone involving a major deliverable in the release life cycle. The processes involved in the release of any deliverables, including submission, planning, ...