Successful Sage CRM with User Acceptance Testing

 

Investing in a customized Sage CRM system is a smart business decision to streamline processes and increase productivity.  Extensive planning goes into working with your Sage CRM consultant to discuss business processes, requirements, QA Testing, and implementation.  However, the final step to a successful project is successful User Acceptance Testing (UAT).

Your Sage CRM consultant will work with project stakeholders throughout the project, but successful UAT testing is dependent on the resources of your organization.  This requires planning and coordination for success.

Whether the project is large or small, the software testing life cycle (STLC) is roughly broken down into three components:

  1. Test Planning
  2. Test Design
  3. Test Execution

Test Planning and Test Design should begin early in the project and your Sage CRM consultant should take lead on these items.  However, successful UAT planning requires the project stakeholders for your organization to actively participate in reviewing requirements, reviewing specifications, and providing feedback long before UAT begins.

Planning is an in depth process, but at a minimum the Test Plan should document the five W’s and one H:  Who, What, When, Where, Why, and How.

Who will execute testing? 

  • Identify the resources who are most qualified in the specified business processes that are aligned with the Sage CRM entities and customizations.
  • Don’t assume the identified resources will be available when UAT is scheduled to begin. Work with fellow stakeholders to communicate with management in order to coordinate and secure a commitment to assign selected resources to the UAT team.
  • Additionally, discuss securing resources for the defined UAT time period.

What is being tested?

  • The fundamental objective of testing is to verify the application conforms to the defined specification and requirements.
  • UAT testing is testing from the viewpoint of the end user. UAT is the process of testing the implemented functionality and verifying it supports the project defined requirements and specification.  For example, the “what” being tested may be as simple as verification of screen modifications or as complex as load balancing and performance testing.

Where in the Software Development Life Cycle (SDLC) will testing occur?

  • Software testing should occur throughout multiple phases of the SDLC.
  • Ideally testing will begin with developer unit testing, move to Quality Assurance testing, and ultimately end with UAT Testing.
  • Plan where testing activities will occur throughout the project.

When will testing occur:  Test-First (before code complete) or Test-Last (after code complete)

  • Test cases can be written before the code is complete or after the code is complete.
  • Test-Last helps users verify the functionality is working as expected.
  • Test-First helps identify how the coding should work.
  • UAT testing is late in the testing life cycle but UAT test cases should be defined well in advance of the start of UAT.

How will testing be completed: Automated vs. Manual

  • Software testing can be performed manually or via automated testing executed by a computer.
  • Automated testing is valuable in testing performance or repetitive test cases where minimum change or user input is required.
  • All tests cannot be automated.

 

Planning is critical to the success of any project and UAT Test Planning is no exception.  Test planning is not a static process and must be updated on demand as needed, but the more detailed the planning, the more successful your UAT test experience will be.