The Importance of User Acceptance Testing

If you are implementing SAP Business One, or any other ERP solution don’t downplay the importance of user acceptance testing.

Most implementation methodologies will include user acceptance testing as a core component. In the early days of ERP projects the implementation team used to focus on a parallel run of the new and old solution. In more recent times this has given way to an updated methodology that includes user acceptance testing rather than a full parallel run. The logic behind this is simple – most small to medium sized businesses don’t have the internal resources to do a full parallel run of two systems. The time taken to enter every transaction into two separate solutions (the old ERP solution and the new) will drain the energy from even the most enthusiastic ERP implementation team. As a result most small to medium sized businesses opt for an approach that allows for comprehensive user acceptance testing is stages or “gates”.

This user acceptance testing is mapped out in a user acceptance test plan. This plan details what will be tested, when and by who. Functional components of your SAP Business One solution are itemised for relevant team testing. For example one part of the test plan might call for accounts receivable invoice testing. A few hours will be set aside for users to run multiple test scenarios:

  • Add in a single page invoice
  • Add an invoice with discounts
  • Add a multiple page invoice
  • Add an invoice with freight
  • Add an invoice from a sales order
  • Add in a single page invoice
  • Add an invoice with discounts
  • Add a multiple page invoice
  • Add an invoice with freight
  • Add an invoice from a sales order

Users will test these scenarios with live data and will record the results to give these functions a pass or fail as part of the SAP Business One user acceptance testing. If a particular function fails, the testing it will be re-worked by the SAP Business One implementation team and the SAP Business One super users for re-testing.

These test cases are carried out across the system. More emphasis is placed on critical components of your SAP Business One solution. For example, if you are a distributor then a lot of testing will be done on the receipting, dispatch and shipping of goods to and from the warehouse. This will ensure that the relevant processes in SAP Business One are well understood and are streamlined for efficiency.

We can see how these smaller components of user acceptance testing take less time and are more efficient and manageable than a full parallel run of two ERP solutions.

The challenge is to ensure that the users conduct thorough user acceptance testing. The importance of user acceptance testing is well documented:

  • Ensure processes are streamlined
  • Ensure that the newly implemented SAP Business One solution will be functional in all key areas
  • Assist with user acceptance
  • Compliment user training
  • Provide confidence to users that the system will be ready for go live
  • Provide the SAP Business One implementation team with time, prior to go live, to fix any configuration issues
    Ensure a successful go live

The team at Leverage Technologies has implemented more than 200 SAP Business One implementations and I can say that the go live process has been a smooth transition for customers. This successful transition has been made possible because of multiple elements in the implementation methodology of which user acceptance testing is core.

User Acceptance Testing - SAP Business One
Share