ERP Testing

ERP Package-led transformation programs involve changes to existing applications and business processes, and interfaces with legacy and third-party applications. Such programs impact a large number of end-users and stakeholders, making decisions related to the scope, time and type of testing critical. Consequently, quality assurance and testing are major challenges in ERP Package implementation and upgrade programs.

The dynamic business environment requires ERP packaged applications to undergo multiple changes during the support and maintenance phases. It results in substantial increase in effort spent on regression testing, which is crucial in ensuring the availability and quality of the application.

SoftLabs ERP testing and validation practice offers services across the life cycle of ERP programs, implementation, rollout, upgrade, production support and maintenance, through testing professionals specialized in ERP packages, IP, innovative solutions, tools and accelerators. Our domain expertise and experience enable us to deliver quality, speed and cost effectiveness in such programs SoftLabs testing and validation solutions span the breadth and depth of ERP packages including SAP, Oracle e-Business Suite, Oracle Siebel and Oracle PeopleSoft. We have a dedicated team of testers with rich experience in industry standard tools for test automation (HP Quick Test Professional, IBM Rational Functional Tester (RFT), SAP Test Acceleration and Optimization, performance testing (HP Load Runner) and test data management.

SoftLabs Advantage

  • An independent Testing Center of Excellence (TCoE) framework that can be implemented across the ERP package life cycle
  • Proprietary testing tools such as Functional Test Case Generator
  • Proprietary business process modeling tools
  • Repository of reusable test assets across the ERP package life cycle
  • Risk Based Testing (RBT) framework
  • Pre-Packaged Testing solutions for SAP, Oracle PeopleSoft, Oracle Siebel For the testing of packaged application the focus is mainly on transactions and workflows. The different types of testing that are performed for packaged applications can be classified as below

Transaction Testing

Transaction Testing is testing of a single transaction (e.g. Create Sales Order) to confirm the operation of transactions and related configuration checks (e.g. default values, mandatory fields, etc.)

Workflow Testing

Workflow Testing (within a module) covers chains of transactions that flow together and which reflect important business process and scenarios (e.g. within the Sales process). Workflow Testing (across modules or external applications) is end-to-end testing of integrated processes through execution of predefined business flows (within the ERP system or collaboration with legacy systems). The different stages of the ERP testing life cycle for testing of package implementations are :

System Study

The project team will analyze the requirements in detail in this phase. The detailed base lined scenarios are an input to this phase. The activities in this phase include.

Understand the business processes, & procedures, business blueprints, FRS documents Business activity scripts. Access the BPP’ of implementation and derive the necessary inputs through those process documents (TCoE) framework that can be implemented across the ERP package life cycle

Work closely with the client SAP team & gather the requirements

  • Identify missing documentation, if any
  • Identify the extent of customization in the application
  • Analyze and list the transactions that need to be automated and to be executed manually
  • Identify the tool that will be used for automation
  • Identify the external applications to which the application under test communicates
  • Risks are identified and dependencies are informed to the client
  • Strategy Planning

The main objective of this phase is to organize, manage and schedule the test effort. The plan is based on the test strategy. The plan identifies the tasks, the transactions/business scenarios to be automated or manually executed and the contingency plans for the identified risks, the schedule, roles and responsibilities and the deliverables from the SoftLabs team. The infrastructure required to carry out the tests is identified.

At this stage the high level scenarios for each are identified and a methodology to test the scenarios is planned. All business scenarios will be signed-off at this point.

Test Case / Script Design

In this phase the test data (master data, transaction data) is prepared by the subject matter experts, test framework is created or reused (in case of a client provided framework), scripts are created (for automation), reused (client provided) and reviewed, and manual test cases are documented (for manual testing) and reviewed. A dry run is executed on the automated test scripts and results compared against manual test cases.

System Integration Testing & Reporting

All test cases (manual) and test scripts (automation) are executed and the subject matter experts and the client analyze the results. Defects are logged and defect reports such as defect trend and summary are sent to the client. The testing team will categorize the automation test defects from the actual functional defects, for automation execution. Reporting will be done at intervals agreed upon by SoftLabs and the client. The reports will contain details on the progress of testing, project metrics, defect statistics and issues faced if any.

Release

On SoftLabs delivering all deliverables successfully, the client will sign off all the deliverables of test automation (test automation plan, test scripts, test data pool, etc.) and deliverables for manual testing (test plan & strategy, test cases, test data) along with the test reports.

UAT

This phase involves in supporting the client for functional & technical issues by the SoftLabs subject matter experts?

Menu Title