Following training, it is important that the client performs on-site testing with their own data, but before the client performs any testing, TMG has already run through a series of routines to ensure that the functionality is running as expected.    Working together with the client, a series of testing scenarios will be created which are typical for the client’s business routine.  Using those scenarios, a TMG consultant will set up this testing environment and provide guidance.  It is the client’s responsibility to ensure that adequate time is allocated for this step.   This is the time in which user procedures are also formalized and documented.

a)     System testing – We will verify with client personnel that the system is fully operational from login to logout and that all module functionality is operational

b)     Integration testing – Once the integrations are defined, TMG will run through a series of data integrations with sample data to make sure that no transactions are failing during the process.

c)     Stress / performance testing – Stress testing is performed toward the end of the implementation but prior to full production go-live.  All integrations are tested with what is expected to be the final import data; each module is loaded with transactions to simulate a live environment, and all reports are run to ensure that they are accurately depicting the data.

d)     User acceptance testing – Once the performance testing is complete, we bring users together with our consultants and run through a series of routines, setup according to the methodology we utilized in creating the testing scenarios.  Each scenario is run by a client and must be accepted in writing prior to moving toward go-live. This way, we will be able to review the entire project and ensure that someone has signed off that they have tested their scenarios and verified that the system is functioning as expected.  Forward steps will not be started until User Acceptance has been obtained.

e)      Lessons Learned – We developed a process called Lessons Learned which is both internal and external.  The client will not be billed for our internal Lessons Learned time, but it is critical to the entire process.  Lessons Learned is a gathering of the stakeholders of the project to discuss in depth any situations that arose during the portion of the project currently being completed.  It may be a discussion with two people or more than 10, dependent on where we are in the process.  The goal is to ensure that we document everything that is an exception to the normal functionality or workflow so that, when the test implementation is complete and we move to the production environment, we have identified any areas that will require special attention and save additional steps and hours.  The Lessons Learned meetings are not held on a regular basis, only when a major piece to the work plan has been completed and User Acceptance is complete.