Cloud for Good
Close this search box.

User Acceptance Testing (UAT) Isn’t Scary!

User Acceptance Testing (UAT) is process of verifying that a solution works for the user. The solution, in this case, is Salesforce and the processes we’ve built together as a function of your project. UAT is where your users get into the tools and make sure they meet your needs.


  1. Create Testing Plan

With our help you’ll build out a list of functions you’d like to test in UAT. Testing should cover each functional area (fundraising, volunteer management, etc.)

The Testing Plan will also include a timeline made up of the dates of testing, the deadlines for issues to be fixed and a deadline for sign-off. The Template below includes an example timeline.

  1. Run Tests

Once the Testing Plan is in place and the team is assembled, testing can begin. The testing team will systematically work through the testing plan, documenting any issues or concerns. This documentation takes place in a shared Google Doc spreadsheet so that multiple users can be testing & fixing at the same time (see template below).

  1. Issue fixing

Issues that arise during testing are addressed by the team and re-tested. This is often a back-and-forth process. It can be easy to get discouraged when you’re retesting a fix for the 4th or 5th time. Know that both teams are working hard to make sure the systems and tools meet your needs.

  1. Sign-off

Once all the testing is completed to your satisfaction, we ask that you sign-off that work is complete.

Template for Testing Plan & Issue Tracking

Who should be involved in testing?

That depends on the scope of your project and the size of your organization. Ideally, each functional area (fundraising, volunteer management, etc.) that is represented in the project will have a representative participating in the testing. For smaller organizations, this might be only one person. We’re happy to advise, but the decision as to who should participate in testing is yours..

How long should it take?

The duration of testing is entirely dependent upon the complexity of your project and your organization. This also depends upon the time testers are able to commit to the process. The testing plan will include a timeline and each functional area should agree to meet the deadlines.

Final sign-off

Congratulations! Now that UAT is complete, you can sign-off and we’ll get training underway. One of the side benefits of a user participating in UAT is that training will be easier to retain because they’ve had exposure to the systems and tools.