User Acceptance Testing for Dynamics 365 Project Service Automation

User Acceptance Testing (UAT) in Dynamics 365 Project Service Automation (PSA) is a critical part of the deployment stage in Encore’s project management lifecycle. After our team has developed a viable solution model and performed our own unit testing, our client’s project team members and subject matter experts perform extensive, hands-on user acceptance testing to validate our design. The UAT process determines whether there are issues that must be resolved prior to go-live, or whether the new system is ready for launch.

Testers receive system user training so that they are familiar with the user interface and main functions of the system. They then follow a UAT script to step through all possible business scenarios related to a functional system area and record the test results.

A UAT script is a formal worksheet or checklist that guides a tester through test scenarios and allows them to report their testing results. Each scenario tested is categorized as “Pass” or “Fail”.

Here is an excerpt from a script used for testing Time and Expense Entry scenarios in Dynamics 365 PSA (specifically for Dynamics 365 PSA v2). This script can be downloaded as a PDF document.

UAT Script elements include:

  • Dynamics 365 Environment: The system URL the tester should use.
  • Security Role(s) required by Tester: The Dynamics 365 security roles required to successfully complete the scenarios listed.
  • Tested By: The name of the person who tested the scenario.
  • Date Tested: The date the scenario was tested.
  • Pass/Fail: The test result. Indicates whether the tester was able to achieve the expected result for the scenario.
  • Area: The functional area within Dynamics 365
  • Scenario: The discrete task or process step to be tested. The level of detail depends on how familiar testers already are with the system, and the training they have received.
  • Expected Result: Criteria for determining whether a test is successful (Pass) or unsuccessful (Fail).
  • Findings: Comments and additional details about the outcome. Findings are typically only used when the scenario fails. Details may include specific records used to test, error messages encountered, etc.

UAT script creation should be assigned to someone who is familiar with the project requirements and who has a thorough understanding of the client’s business processes. Testers should be subject-matter experts in the processes and areas being tested.

The time invested in UAT and test script creation pays off in numerous ways. Testers are equipped and confident that they are testing the “right things”. Testing is consistent across users and over time. UAT scripts created for the initial deployment of a new system can be reused following system upgrades or other changes. Most importantly, UAT empowers decision makers by providing concrete information about system readiness for go-live.

If you have any questions about Dynamics 365 Project Service Automation, please connect with us.

26 Creative Ways Companies are Using Dynamics 365

Find out how companies like yours are using Dynamics 365 to manage their customer relationships and drive revenue.

Get The White Paper

26 Creative Ways Companies are Using Dynamics 365

Get The White Paper