Testing Services provides a platform for QA professionals to discuss and gain insights in to the business value delivered by testing, the best practices and processes that drive it and the emergence of new technologies that will shape the future of this profession.

« Darwin and world of Digital transformations | Main | A.E.I.O.U of New Age Quality Engineering »

SAP Test Automation approach using HP UFT based solution

Author: Kapil Saxena, Delivery Manager

Problem statement
Most businesses that function on SAP, or plan to implement SAP must consider multiple factors, as their entire business runs on this backbone. Their major worries are testing effectiveness, preparedness, cost, and time to market. Infosys SAP Testing Unit has answers to all four, which have been well implemented and proven but I am reserving this blog for the last two.

Companies planning SAP implementation often tries to think delivering in Agile/DevOps model, but we have not seen this model work out frequently. The issues are mostly on the system integration side when the error correction code (ECC) finally interacts with hundreds of legacy systems to make end to end work. I will focus on how we can make pure SAP implementations a possible candidates for agile testing.

Approach to be taken

We chose HP Unified Functional Testing (UFT) to build our solution with a simple reason that it is open to code changes outside the tool itself. It gives our engineers the flexibility to make changes on the fly directly in the code rather than to record the changes again. The testing also provides flexibility  to create reusable functions to handle exceptions and make intelligent logical conclusions based on data collected over the years of testing SAP ECC and learning the behavior. As we all know that testing any system in reality is way different than doing the same in an ideal working environment.

Solution: Our functional consultants gathered a list of the most frequently used transaction codes (t-codes) and their variants from multiple hands on experiences. This helped us create repository of 1,500 reusable t-codes in a solution called Infosys Test Planning Accelerator (ITPA). These run uninterrupted in SAP vanilla systems. We took the next step, and using our proprietary automation framework, automated each t-code. The uniqueness of our solution ensures that we take a maximum of 15 minutes to customize one single t-code to fit into any client landscape. With this solution, any company implementing SAP ECC, gets a pre-automated repository of important t-codes which can be made ready to use in a very short interval of time. This comes in very handy when quick system testing is required. We propose the following approach to our clients in order to achieve close to agile testing:         

  1. Developer makes changes in advanced business application programming (ABAP) code of a t-code and pushes it to the development environment
  2. A tester, who is associated with developers, is intimated about this. He/she runs the automated t-code in this environment. In case of failure, the tester quickly fixes the code and runs it to success in 15 mins. This helps to perform unit testing for as many data sets as possible, thus reducing the chance of any defect in upstream integration. This also makes the t-code ready for later use
  3. Once all the t-codes are updated and unit testing is done, the solution is ready for system testing. In this phase, we arrange all the t-codes for each system, say for example, sales and distribution (SD), in a sequence and run them in batches to ensure that the overall system is working properly. These are again reusable from the previously automated t-codes; resulting in less rework and high reuse
  4. With this, we come to system integration testing. Once we have identified the end-to-end scenarios, our framework has another solution called Infosys Automation Orchestration Platform (IAOP), which stitches the t-codes together to create a complete scenario from different permutations and combinations of the same t-codes. HP Application Lifecycle Management (ALM) gives us the flexibility to stitch them seamlessly, so that we are ready to complete the system integration testing (SIT) in probably half the time as before.

This process of testing SAP system can be used both in waterfall and agile form without any change in the scripts. The only change we request from our clients is in the agile methodology, where we want to be closely associated with each developer and seek access to the code drop in the development environment along with master data.

Business benefits

With two solutions and a unique approach, we help our clients achieve the following:          

  1. Reduction of around 40 percent of efforts on a greenfield implementation by making use of the ITPA (Infosys Test Planning Accelerator) which is a repository of existing t-codes
  2. About 40 percent jumpstart in test automation with pre-automated t-code repository
  3. This process is a set base for any type of testing, be it waterfall or agile so fit for both approaches without any change in process
  4. Considerable reduction in time to market. We have reduced the overall time to complete testing in certain cases by 75 percent, using significant automation and the way we plan and run them.

Know more about our offerings here.

Comments

That's great..In my previous assignment we used HP UFT to automate regression testing for SAP PI Interfaces and we integrated this with ALM.We again reduce the time of testing more than half.Also we extended it further to generate report out of it in pdf..

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Infosys on Twitter