.png)
UAT
The UAT phase begins after the Build Phase concludes, and testing and validation have been completed. At this point, the software is ready to be released for UAT. The Partner UAT focuses only on functional testing since the Medable software has already undergone a robust testing process prior to UAT. The purpose of UAT is to ensure that the software’s major functions perform as specified by the requirements document.
If the Partner chooses to utilize the Medable UAT process, the following workflow is followed:
- The SM prepares UAT devices: the Partner must provide the name, email, and address of each person that requires a UAT device in advance.
- The SM drives UAT planning activities: UAT test accounts and sites are created following the roles defined by the Partner, the SM confirms the Partner has created UAT test scripts, and the SM shares a UAT dashboard with the Partner.
- The SM conducts a UAT Kick off Meeting and trains the Partner users. The Medable team supporting UAT will explain how "time travelling" works in Medable software (triggering a functionality designed for the study that is linked with a specific date and time on the workflow).
- UAT is executed.
- The SM coordinates the UAT feedback with the Partner and address all the comments. Any scope changes from the UAT feedback are reviewed with the Partner and timelines, budget and feasibility are discussed. Any identified defects are fixed, tested, and released for retesting and the SM confirms with the Partner if additional rounds of testing are needed.
- UAT Sign-Off and Completion: the SM completes the User Acceptance Testing (UAT) Approval Form and both parties sign the document.
Testing
The Medable team works internally to drive issue resolution of any issues identified during the test cycle.
Regression testing is completed to ensure that any recent changes do not affect existing features, and smoke testing is completed to ensure that the products' core functionalities operate properly.