Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

SAP Test Automation – Solution Approaches

Posted on: 16 August '10

Reduce maintenance effort to address test case flow changes

Let us see the maintenance effort involved in the approach of keyword implementation that I mentioned in my previous post. If the test data changes or to run the same scripts using multiple test data sets, we will not have to change the automated scripts. If a business process like “Procurement to Pay” involves additional transactions or change in flow of transactions, we just have to rearrange the transaction level keywords. However, if a particular transaction flow changes or some additional fields are included, it would require modifications in the code associated with the transaction keyword. However small the effort may be, manual test engineers or functional consultants would not be comfortable in doing them; automation engineers have to be involved.

We can avoid this by implementing keywords at a SAP GUI widget level, like “SAPGUIEditBox” for text box, “SAPGUITable” for table etc. We also have to implement keywords for the actions to be performed like “Click” to click a button, “Set” to enter a value in the edit box. So a combination of keywords along with widget identifiers can be used to perform specific actions and verifications on each SAP screen. These keywords can be organized to form scripts corresponding to higher level keywords like TCodes.

If any transaction flow changes or additional fields are included, functional consultants can easily make those changes in spreadsheets or GUI input. The involvement of automation engineers is reduced since the keyword codes once developed would not change across the SAP screens since the technology used to develop them is the same.

My next post will talk about approaches for execution and management of the automated test cases.