Right way of ERP testing importance

Testing
Everybody got amazed when a software program blows up the first time it is used, even though those who developed the program insist they previously tested it? Now multiply this situation by hundreds of ERP Programm that were "tested," and then imagine the pressure at production. This scenario as usual.

Conference Room Pilot

The Conference Room Pilot is the first stage of formal testing. It is mainly disturbed with testing the programs within each software module. As with any testing, this comprises the standard programs that come with the package and all custom developed programs.

Each application team is accountable for testing their software module during CRP. The concept is to first test each module of the system individually to protect it is working properly before adding more problems.

Integrated Conference Room Pilot

The Integrated Conference Room Pilot is that where it all comes together for the first time in the system. The goal is to test all software modules functions together. Just because independent modules work fine when tested individually during CRP, but it does not mean they work well when interacting with one another.

Test Cases

According to different business process, there are many scenarios may occur. In the sales order example previously discussed, there will be order cancellations, back-orders, and pricing issues, to name a few. Sometimes there are many scenarios may occur a single day, let alone, other things that happen less frequently. Moreover, the business scenarios are not mutually exclusive. Many can occur at the same time, and unique customer needs always add a different challenge.

Testing Over-sights

Common pitfalls during CRP and ICRP testing:

Failure to Unit-Test Custom Programs in Advance. Many of the standard programs within the package have been unit tested prior to CRP as part of the pattern and the design phase. However, this is usually not the case for programs containing custom code.

User Acceptance Test (UAT)

At some point, the power users and major stakeholders should participate in the CRP and ICRP. But once this testing is complete, they should be responsible for organizing more end users to conduct a separate user acceptance test.

Limited Parallel Pilot Test

This type of navigator is not performed in a conference room but within the actual work area. It is limited in the sense that it occurs within a contained area of the business, and it lasts only a few days or maybe a week. It is parallel since it involves end-users using both the new and current system concurrently.

Volume or Stress Test

When system performance or stability issues arise at any time, do not ignore them. Beware of the system is slower or crashes periodically during testing or end-user training. You had better find out why and address the problem because there will be many more users beat the system when it is in production.

System Cut-over Test

When it is time to cut-over to the new system, usually the business operations must cease for a particular period of time in order to get a clean transition from the old system to the new though normally some early change steps can occur while the business is still running.