Support Central
Learn how to implement test plans in a real-world example, where the test plan is created and managed by the subcontractor.
In this example, the main contractor for a multi-story apartment needs to ensure all piling work is completed to a high-quality standard. They need to track progress, review the work at important milestones, and capture all evidence 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.
This use case is just one example. Test plans are highly configurable, allowing you to assign different responsibilities to many different organizations. Read the Get started with Test Plans article to understand how test plans works in Aconex. If you need help with implementation, our Professional Services consultants can help you with process discovery and mapping.
There are three organizations participating on the test plan:
Within these organization are users with different roles and responsibilities throughout the test plan process.
The diagram below shows the overall process.
The subcontractor creates and activates the test plan, works on activities, and marks them for review. The consultant verifies the work and the subcontractor marks the activities as complete.
The subcontractor submits the test plan and the main contractor closes it.
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 subcontractor organization has users with the following test plan roles:
The subcontractor is also assigned the following participant roles:
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 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.
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.
