We understand that the ERP packaged application testing needs time to deliver the best, however it is possible to enhance productivity by accelerating various testing events throughout the testing life cycle.

1. Best ERP Testing Practices
for Large Organizations .
Technical White Paper

2. Have you ever given thought as to why serious software failures
occur after go-live, even though the vendor who developed
the application insists on it being tested hundred times?
According to leading IT research firms, critical enterprise
packaged applications like SAP, Oracle and Microsoft impact
a broad set of stakeholders. Coordinated testing across this
group is a critical requirement in the application launch plan,
but many miss the mark when planning for these mega
critical projects. The reason why many packaged application
implementation projects fail is improper test planning and
execution.
Packaged enterprise applications are mission-critical and with
now steady shift to cloud, it has become absolutely vital to
monitor the applications with regular QA checks. This also
demands for the QA best practices to be followed to manage
these large scale mission-critical applications. Testing on ERP
packaged application systems is normally conducted during
deployment and continues even after going live.
Best Practices in ERP Testing
While testing large scale packaged applications, best results are achieved with a holistic approach. Such testing encompasses
many departments within the company, and many modules.
Before getting into ERP packaged application testing, the testing professionals need to understand the concepts, processes,
strategies, and the criticalities of ERP packaged application testing.
Let us look at some of the best practices of ERP packaged application testing that include doing everything right from test
planning to generating test reports.
Providing data for ERP packaged application testing activities
There are four main challenges with respect to the provision of test data for automated ERP packaged application testing–
system test data supply, system test data stability, system test data co-relation, and test data management.
• Test data supply:
ERP testing normally demands the insertion of common test data to the system during test preparation.
• Test data stability:
Use the system data access rules to prevent alteration of common test data.
• Test data co-relation:
The relationship between system data and input data needs to be observed.
• Test data management:
A test data management system provides the capability to correlate and analyze test results from several groups at
different locations and time zones to quickly access and assess the information they need.
Define test goals and select appropriate tests
By thoroughly defining and creating primary testing goals we can clearly determine that a particular type of testing that is
required and the resources needed to execute in a certain time frame.
• Define objectives to meet test goal:
Analyze the requirements, decide the type of testing needed, set the testing goals, and define the objectives that will
help you achieve your goals on time.
• Identify test cases:
Identify all the test cases for the different types of tests to be performed, and then generate the test cases covering the
entire testing scope.

3. Conclusion
We understand that the ERP packaged application testing needs time to deliver the best, however it is possible to enhance
productivity by accelerating various testing events throughout the testing life cycle. The test accelerators help in areas such
as detecting defects in the requirements phase, web series testing, and browser compatibility testing help jump start with
QA efforts and ensure quick returns on investment.
YASH-ERP-Testing-WP-1217
© 2017 YASH Technologies. All rights reserved. Referred products/ services may be registered trademarks of belonging companies.
About YASH Technologies
YASH Technologies focuses on customer success. As a leading technology services and outsourcing partner for large and fast growing
global customers, the company leverages technology and flexible business models to drive innovation and value throughout its customer’s
enterprise. YASH customer centric engagement and delivery framework integrates specialized domain and consulting capabilities with
proprietary methodologies and solution offerings to provision application, infrastructure and end user focused Right-Sourcing services.
YASH is a SEI CMMI (Level 5) and an ISO 9001:2015 certified company with U.S. and India headquarters and regional sales and development
offices globally with customers spread across 6 continents.
.
YASH Technologies Global Presence www.yash.com/contactus
AMERICAS | EUROPE | APAC | MEA
World HQ: 605-17th Avenue East Moline IL 61244 USA | Toll Free: 877-766-8934 | Tel: 309-755-0433 | Fax: 309-796-1242
For more information contact YASH today at info@yash.com or visit www.yash.com
Document key business process
Thoroughly document all the business processes in the organization that are implementing the ERP packaged application.
These processes will be the test scripts and every test script should satisfy a process or a set of processes.
Develop modular test components
Developing modular test scripts enables to unit test all the modules and the customizations made to the ERP system
modules before the entire system is completed.
Set up a test lab
As a best practice, it is strongly recommended to set up a separate quality assurance test lab as a part of overall strategy for
testing and refining the ERP packaged application.
Leverage smoke testing
Building a smoke test for critical business processes which is generally a combination of manual and automated tests that
can run quickly, helps you identify gaps in the processes.
Execute Regression, Performance, Security Tests
When it comes to ERP packaged application testing: Regression testing, Integration testing, Performance testing, Usability
and Security testing gains prominence as the system holds mission critical data of the organization.
Analyze defects and create test reports
As the test sets are executed, we must track and analyze the failures that occur within the tests and their location in the
business processes. All this information should be neatly documented and presented in the form of test reports.