[Video] Best Practices for User Acceptance Testing in Dynamics GP

Visit Website View Our Posts

User acceptance testing is a frequently missed step in a Dynamics GP implementation that has the potential to make a launch go much smoother. After all, nobody wants to spend hundreds of hours and thousands of dollars implementing a system, only to have the users not adopt it at the end.

Instead of just hoping for adoption, user acceptance testing allows you to ensure the requirements – hopefully! – laid out at the beginning of your project are met and that you users have a voice during the implementation. So, with that in mind, here are four secrets to a good Dynamics GP user acceptance test.

  1. Train your testers before they test

Users need at least basic training on how to use the system before they do their user acceptance test. Without it, they’ll need click-by-click instructions to get through their processes, which is time consuming and doesn’t provide real results.

  1. Provide detailed testing scripts

Give each user a detailed testing script of what they need to test. If you just give them a carte blanche, they’ll either neglect the test entirely or deliberately try to break the system. Neither of which provide meaningful results.

So, what you need to do is to outline in detail the processes that they use every day. Then, have the user mark off each of the items that they successfully test, to verify that each function works.

  1. Test using real data

You want users to do a realistic test of their every day transactions. If the person does sales orders or purchase orders, have them grab a stack of the ones that they did last week and replicate that in the new system. If they do importing, have them actually run one of the previous imports to ensure everything populates.

  1. Support users during testing

Users need support during the whole process of user acceptance testing. It is a brand new system to them, and you're trying to test whether the system works. You're not trying to test the user's knowledge of it.

You don't want them to get into a space where they get stuck, then frustrated and say, "The system doesn't work." Help them along through the process and you’ll avoid false claims that something is broken when it was just misunderstood.

Are you looking for some more advice on how to do a great user acceptance test? Talk to Prophet Business Group or check out our other blog on the topic.

- Tracey Wright, Software Consultant, Prophet Business Group - Dynamics GP, Dynamics 365 and Office 365 in Central Canada

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Show Buttons
Hide Buttons