BTerrell Group Blog

Three Common Reasons for Not Doing Implementation Acceptance Testing

Posted by Chris Firra on Tue, Oct 07, 2014

User acceptance testing is an extremely important part of a successful accounting system implementation. The testing phase is typically carried out just prior to live deployment, and if done correctly, it eliminates the risk of failures in critical business functions that depend upon new accounting systems. Despite this, there are always pressures to reduce the scope and depth of testing. Here are a few commonly cited reasons:

The user resources are too busy and just can’t be spared 

User acceptance testing, as its name implies, relies upon the expertise of the accounting systems users. While developers and implementers can carry out systems testing, the system’s real users best understand the business applications. For this reason, acceptance testing must be the responsibility of the client and its staff.   

We’re deploying published standard software that has little risk of failure

While it is true that the risk of application failure is often low, the purpose of acceptance testing is to determine if the new system has adequate functionality to meet business requirements, which is quite different from simply determining whether the software works as designed. Additionally, the acceptance testing provides an opportunity to determine if users have the know-how to operate the software.

Faults can be corrected after go-live

Solving system issues in production is more expensive and certainly more stressful than correcting system faults prior to go-live. In a post-go-live scenario, the quickest solution usually is deemed best. However, if the problem is detected earlier, more and often better options can be evaluated.

The long and short is that there is just no alternative to adequate user acceptance testing. It should be planned and carried out by the client and its users of the new system. BTerrell’s implementation team plays an active role by providing guidance and user support during this very important phase.


Tags: successful software implementation, software testing, implementation