Testing ERP Package

A unique way
Project Code: CISQTCIV/CISQAQTC Project Type: Testing H/W: Windows PC S/W: Oracle 11i

Testing ERP Package

Is testing ERP Package easy?

Testing ERP Package

There is a misconception that testing ERP package is easy and fast. The reasons for this misconception are as follows:

The ERP Package is highly customized and hence testing such a customized system would be trouble free and will have less defects.

Customization Process itself will take care of the errors in the Package and as a result the Package will have less or zero number of defects !!!!!

Testing ERP Package

The reality about testing ERP Package

Testing ERP Package

Testing an ERP Package is a difficult task as it involves the integration of many business flows. Testing an ERP Package is different as here the testing is of the integration of the Package along with the functionality and not only of the functionality!!

Also since the ERP Package involves many business flows right from placing the order to invoicing and posting to the companys revenue, we need to ensure the processing is smooth through each flow involved.

Testing ERP Package: Correlation Factor

ERP Package application is a tailor made application which should be tuned and adapted well to the Organization, i.e. there should be a higher degree of correlation between the ERP Package and the Organization.

Testing ERP Package: Risk Factor

ERP Package involves the processes that flow across the entire organization, the risk factor involved is very high. Hence the testing should ensure that each process and the integration is tested with greater accuracy. The risk should be identified and weighed also and accordingly the Mitigation plan should be created. Testing Structure, Different levels, techniques and tools for testing, environment selection, defect management, test process management are the factors to be taken care during the testing of ERP Package.

Testing ERP Package: Security Factor

Since the ERP Package includes the business rules of the organization, the exposure to the ERP rules and the database would be limited and as a result the ERP package will be black boxed to certain limit, thereby making the testing difficult.

Testing ERP Package: Parallel Execution

Since ERP testing is the testing of different business flows and their integration, division of the team according to the flow would be helpful as a single team testing ERP package would require the team to know a lot of processes. Hence ERP testing requires parallel execution. Also the parallel execution would result in an efficient and faster testing. For example, consider that OC (Order Creation) has successfully created an order. Now Auto-Mfg team takes care of the Manufacturing process. Meanwhile, OC team can continue with the next orders.

Testing ERP Package: Real Time Testing

For making the ERP testing effective, the real time scenarios should be identified and should be verified against the estimated duration of the execution. The scenarios can be from placing an order to posting it to the revenue of the company.

Testing ERP Package: Test Planning

The Test Planning in case of the ERP Package should be effective that should cover all the aspects of all the business flows and rules. Object Oriented Approach for Test Planning is an effective way of creating the Test Sets for ERP Package since the same processes will be involved during the testing. So the common processes can be created and than the specific functionality scripts can be added to the common scripts to create the Test Scenario.

Testing ERP Package: Data Generation

Data is the heart for the ERP testing. Valid data based on the requirement should be available for the testing. Backup of the data would be helpful as many flows working on the same database might change the data and the to be used data might become invalid for other flow. For example, suppose accounts department needs a customer with order limit amounting to 1,00,000 $. Say xyz satisfies the limit. Now if order creation flow creates orders for xyz worth 50,000 $. As a result the data becomes invalid for Accounts department.

Testing ERP Package: Communication

The communication should be effective and efficient the different flows for a faster execution. For Example, once the OC team completes the order, the Auto-Mfg should be intimated ASAP so that they can complete their task.

Testing ERP Package: Defect Fixing and Retesting

Due to the integration of many flows, the defect fixing becomes a tiresome job as the first priority is to find out the flow where in the defect is. Later comes the fixing part. Hence the defect fixing might take more time and hence extending the testing duration. Also retesting the defect on time is a critical part. The retesting should be done as soon as the defect is fixed and is ready for retesting.

Testing ERP Package: Data Integrity

The Data Integrity should be well maintained between the data tables. For example, the orders which have products shipped should also be present in table of booked orders. The order which is invoiced, invoice/invoices should have been generated for that order and the invoice number and sales order number should be maintained in a table.

Testing ERP Package: Regression Testing

ERP Package is also known as the Patch ware due to the patches after the development. Since Patches can break the integrity among other domains, there is a need to retest the entire scenario. As a result each time a defect is fixed, the entire functionality should be retested to make sure that the defect fixing has not affected the other business processes.

Testing ERP Package: Training

Since ERP Package involves various business processes, providing training to the people testing the application takes a longer duration. The training being provided should be effective and complete so that they can understand what should be the behavior of the system.

Testing ERP Package

Overall ERP testing:

Should be done with care. Real time scenarios should be identified. Communication is a key factor for ERP testing. Data is the heart of the ERP Testing. Test planning is critical. Object Oriented Approach is a great help. Risks should be identified and handled. Effective training should be provided to the end users. Regression testing done for each patch or modification.