Support Central
Learn how to implement test plans in a real-world example, where the test plan is created and managed by the main contractor.
In this example, the main contractor for a multi-story apartment needs to ensure all air conditioning systems are installed to a high-quality standard. They need to track progress of the installation, review the work completed at important milestones, and capture all evidence of the installation to handover to the client. The test plan template has already been published with the appropriate organizations set as the Assignee(s), Reviewer(s), Manager, and Approver.
There are three organizations participating on the test plan:
Within these organizations are users with different roles and responsibilities throughout the test plan process.
The diagram below shows the overall process.
The main contractor creates and activates the test plan, marks activities as complete, and closes the test plan. The subcontractor works on their activities, and the consultant verifies their work.
The dotted line represents the lifecycle of a single activity. In practice, a test plan will contain multiple activities.
Open the diagram in full screen in a new tab
In Test Plans all users are assigned a test plan role to determine what actions they can perform. In addition, a user or organization is given a participant role on a specific test plan so they can work on it. Learn the differences here.
For this use case, the roles in each organization are configured as below.
The main contractor organization has users with the following test plan roles:
A Contributor who creates the test plan from the template.
The main contractor is also assigned the following participant roles:
The subcontractor organization is set as the Assignee of each activity. They complete the work (for example, installing the electrical wiring), attach evidence, and mark the activities for review.
After the test plan is activated, a user with the Associate (or Administrator) test plan role will reassign each activity to specific users within their organization.
The consultant organization is set as the Reviewer of the activities. They check the work of the subcontractor and complete the reviewer actions, such as Hold Point or Witness Point.
The consultant users have the Associate test plan role. This allows them to complete or reassign the reviewer actions where their organization is set as the Reviewer in an activity.
After the test plan has been activated, both the subcontractor and consultant organization reassign the activities and reviewer actions to specific users in their organizations. This ensures everyone involved in the test plan knows exactly who is responsible for each activity.
The Assignees work on their activities. They open the mobile app to view the requirements for installing the air conditioning system. For simplicity, we'll demonstrate what happens in a single activity, but in practice a test plan will contain multiple activities that are started, reviewed, and completed before the test plan is submitted.
Every action that happens in the test plan is recorded in the event log. This is an immutable audit trail that cannot be edited or deleted by any organization. At any time, any user can view the test plan event log to understand the decisions that have been made up to that point in time. This provides a complete record of the work and a single source of truth when resolving disputes.
Test plans can be exported as a zip file to retain a record of files and evidence or to use as handover documentation. Exported test plans include inspections, attachments and linked documents within the activities.
