Best Practices for Product and Solution Testing

Product and solution testing is often the first task to be ignored, shortened, or even just removed from scope when trying to complete a new software implementation on time and on budget. However, effective testing can save your organization significant time and resources over time by identifying and eliminating issues before they become large problems. That’s why it’s so important to complete all testing phases and tasks during the implementation.

In this webinar, RPI Senior Solutions Architect Pitts Pichetsurnthorn and Project Coordinator Sean LaBonte share our best practices and recommendations for effective testing across all types of implementations, upgrades, and solution optimizations.

Download PDF

Welcome to Webinar Wednesdays with RPI, and thank you for joining the best practices for product and solution testing. This is part of our Webinar Wednesdays series here at RPI. We do webinars the first Wednesday of every month. Today we’re going over our testing best practices, and right after this we’ll go through our Brainware for Transcripts at 1:00.

Next month in September we have a couple of webinars planned. The big one is our 7.2.3 release of ImageNow or Perceptive Content. Sean will be going over that release and the learn mode updates as well at 11:00. Then at 1:00 p.m. we’ll be going over our new Yoga Link product, which is built to work with Yoga but it’s really a Chrome extension that’s going to allow you to link directly out of Chrome into your learn modes.

As I said, my name is Pitts. I’m a senior solution architect here at RPI. I have a little over six years of experience working on the Perceptive Content platform, extensive experience really within the clinical health care space, so I know a lot about the clinical products and the solutions that we use within that vertical. I love my dog Tofu.

Sean LaBonte:
My name is Sean LaBonte. I’m a project coordinator with RPI. I manage multiple projects including upgrades, health checks and new solution designs. A little bit more of a cat person, and on an unrelated note I am still Kansas City’s most eligible bachelor. On today’s agenda we’re going to cover a little bit about us, RPI Consultants, and go into introduction of testing methodology, the testing stages involved, and the management portion of those.

At the end we’ll have a summary and a section for Q&A. A little bit about us, we’re a comprehensive professional services organization with almost two decades of experience designing, implementing, and supporting ERP, ECM, and advanced data capture solutions. We have over 80 full-time consultants, project managers, and technical architects, several different locations for offices across the US.

We provide services including technical strategy, design enhancement, support in the realms of Perceptive, OnBase, Brainware, Kofax and Infor.

Perfect. Introduction to testing methodology. Testing is a vital part to every project we do here at RPI. While it’s often overlooked because it is a pretty tedious process, it’s very vital in ensuring that the solution and the products that we’re implementing go smoothly. What we wanted to go over here was really just a high-level overview of what we do as far as testing, and how most of our projects become successful because of the amount of testing that we put into it.

With testing, there’s four main principles here, four main objectives for every testing cycle that we do. The first one and probably the most important one is provide visibility for the stakeholders. The stakeholders that have made the decision to purchase the product or purchase the solution, to bring that into the day-to-day lives of your end users. They need to be up to speed with where everything is at, what are the flaws, where the status of the project’s at before we actually go into cut over and go live.

The other main point here is that we like to identify any failures or any bugs or defects, log those so that they could be corrected and addressed. We also want to ensure that the solution meets those functional requirements. We’ll go through a design. As we gather our business requirements, and then when we develop these components and these solutions we want to make sure all of that is going to address those functional requirements.

Then the last one here is that we want to make sure that there are no undesirable side effects as a part of introducing this new solution. Now, testing is not a one-size-fits-all, but we all have the same goals here with our testing efforts. How do we accomplish this? This is done through using a variety of resources. Again, these are users or tools. As we go through our testing cycles, we bring in different sets of users so that more people on the client side could be exposed to the new solution.

We also use a variety of tools to help w