Tuesday, December 18, 2012

How we can increase the automation coverage and minimize inconsistencies between automated scripts & manual test process flows. A good way would be to enable business/functional consultants to contribute towards SAP test automation, in terms of creating automated test scripts, maintaining and executing them with minimal learning curve.

The automation engineers would develop the automation framework and SAP specific reusable components. The functional consultants would use and organize them to automate test cases and process flows on the fly.

This approach can be implemented by developing a hybrid test automation framework that supports both data and keyword driven automation methodologies. In the data driven approach, the test data is separated from the test scripts and each test script can be executed iteratively for various data value combinations. The keyword driven approach involves coming up with action tables using keywords to interact with the application under test.

Keywords can be implemented in different ways. Usually, keywords are implemented at business function or transaction level. For e.g., “Create Purchase Order” or “ME21N can be a keyword with associated parameters like PO type, Purchasing Org etc. Similarly ReleasePO can be another keyword with its input fields as associated input parameters. Create Purchase order, Release Purchase order and other transactional keywords can be organized in the appropriate flow to automate a business process. Each keyword has associated script developed in the language of the automation tool used. These scripts are developed by automation engineers. To automate a test case, we would use these keywords in a specific format & order and enter the test & verification data for the transactions via a GUI or spreadsheets, based on the framework implementation. Often spreadsheets are used because of their popularity.

Once the framework has been developed, business consultants can start automating and executing the test cases with minimal knowledge of the tool or framework implementation. The automation engineers can get involved only if additional application specific functions have to be developed. Thus, with the participation of business consultants, automation coverage is increased.

Challenges

Record playback approach towards automation rarely use it considering its limitations in terms of re-usability. Let’s assume that we have scripted and parameterized the test cases and no test data is hard coded. So we can run the same scripts using multiple test data sets without having to spend effort in changing them. But what if additional fields are added and the test case flow changes. It would involve modifying the script code and it would involve engineers who are well versed with the tool’s scripting language.

Test automation is often done by engineers who are well versed with programming concepts and automation techniques, but not with business processes. The ideal situation would be business analysts or functional consultants automating the test process flows, but unfortunately, they do not have automation experience. Also, in SAP testing teams, automation engineers are usually not many in number and they are shared across projects, because of which the rate of automation and coverage is low.

SAP Test Automation with QTP

Client / server side settings.

These are the basic settings you need to enable scripting on your SAP GUI for windows apps.

1) Client side setting.

2) Server side setting.

Client side setting: Upon logging on to the SAP R/3, click on Customizing of Local Layout SAP toolbar button as shown below:

And click on Options. The following (Options) window opens. Navigate to Scripting tab and select "Enable scripting" checkbox and deselect the other two options below the "Enable scripting" checkbox. This completes enabling client side scripting.

Server side Setting: Run the transaction code RZ11, this opens Maintain Profile Parameters page, enter "sapgui/user_scripting" and click on Display button.

this opens "Display Profile Parameter Attributes" Page.

Check if Profileval is set to TRUE else click on change value button and change the value of Profileval to TRUE.

This completes our Enable scripting process.

Following problems get resolved during SAP Automation with QTP 10.0 & QC 10.0.

1) During creation of Handling Unit (HU) in LM00 transactions, SAP takes more than 2 minutes to process the data. This causes QC to throw a “Catastrophic failure” and stop further execution. I tried inserting a “Wait” but it still isn’t working, I googled this error and found the following post, but the solution still doesn’t exist.

Done R&D on following link but due to some reasons could not get success,

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1282469235113+28353475&threadId=1364983

Solution:

After installing patch QTP_00684.EXE, Released by HP and making the necessary changes in mic.ini, the problem seems to have been fixed.

2)http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1307099472115+28353475&threadId=1446685

Business Process Testing with QTP by Sandip.G

Business Process Testing combines two roles, the Subject Matter Expert (or Business Analyst) and the Automation Engineer, to create reusable Manual, (and then Automated) Components of a test. The SME creates the description and steps of each component, how it operates, it's valid input and expected results. The automation engineer (or the SME) can convert the manual components to simple high level Automated Non-Scripted Components. The automation engineer can use QTP, if necessary, to convert Components to more complex Scripted Components.

Business Process Components are created initially in Quality Center, and the tests they comprise are created in a drag and drop building block manner of these components. Similar to Actions, Business Components address a single business aspect of a test, such as Logging In or Performing a Product Search. Like Actions, they support parameters for flexibility and scalability. You might use different User names and passwords, or search for different types of media by title or artist, respectively. Tests are then built by stringing together reusable component modules, reducing maintenance at a modular level, all inside Quality Center.

Automated components come in two flavors: Non-Scripted (the default) and Scripted. Non-Scripted Automated Business components can be created from Manual components inside Quality Center, and are just the high level capabilities of QTP, displayed in a view similar to QTP's Keyword View. These Non-Scripted automated components lack the ability to add decision logic. This keeps complexity at a straight forward level, so that non-developers, such as your SME, BA or Manual Testers can create automated components. However, they can be converted to Scripted Components within QTP, where the Automation Engineer can add more complex decision logic in the Expert View.

Business Process Testing also includes Application Areas. This is where the additional support functionality of these components are created and managed by the Automation Engineer. This includes the familiar aspects of QTP including the Object Repository, Recovery Scenarios and VBScript Library Files.

One advantage of Business Process Testing scripts is that since they retain their manual step descriptions, so they can be executed step by step by a manually tester, even after they have been automated.

CRM Click WebButton

Given below code will work for the clicking for CRM WebButton .

Public Sub CRM_Click_WebButton(obj_container, str_WebButtonID)
Dim i
Dim j,m
Dim objs
                'gets all Links from container
              Set objs = obj_container.Object.documentElement.GetElementsByTagName("BUTTON")
    'for each object - check if the expected link is found
                For j = 0 to objs.length - 1
     If Instr (1,objs(j).id,str_WebButtonID,1)>0Then
      objs(j).Click
     End If
                  Exit for
    Next
       End Sub

Wednesday, October 3, 2012

Order to Cash Cycle -Flow

A customer orders some items from your company by creating a sales order (Tcodes: VA01, VA02, VA03, Tables: VBAK, VBAP etc).

Your company decides to deliver the items ordered by the customer. This is recorded by creating a outbound delivery document (TCodes:VL01N, VL02N, VL03N, Tables: LIKP, LIPS etc).

Once the items are available for sending to the customer, you post goods issue which reduces your inventory and puts the delivery in transit. This will create a material document. You will post goods issue using VL02N but the material document created will be stored in tables MKPF, MSEG.

You will then create shipment document to actually ship the items. (Tcodes: VT01N, VT02N, VT03N, Tables: VTTK, VTTP etc).

You finally create a sales billing document. (TCodes: VF01, VF02, VF03, Tables: VBRK, VBRP etc). This will have a corresponding accounting document created that will be in BKPF, BSEG tables.

When customer pays to your invoice, it will directly hit your AR account in FI.

You will have to remember that these are not a required sequence. Some times, you may configure your system to create a SD invoice as soon as you create a sales order or you may not create a shipping document at all. This is the position where Functional Consultant would come into picture and study the company's order to cash process and configure the SAP system to do so.

---By Nageshwar

Wednesday, July 11, 2012

About HP BPT

HP Business Process Testing

Automated testing can be used in an environment with multiple SAP Applications, Ex. R/3, SAP SA, SAP FI, EBP, BW, etc. It also covers the usages and requirements which are critical to deploy an Automated Testing solution. This article will help Consultants alike gain insight in the application of Automated Testing in an SAP Environment and help to bring the best return on investment.

HP Business Process Testing

Understand Business Process Testing

Business Process Testing is a role-based testing model that enables Subject Matter Experts—who understand the various parts of the application being tested—to create business process tests in Quality Center. Automation Engineers—who are experts in Quick Test and automated testing—use Quick Test to define all of the resources and settings required to create business process tests. Integration between Quick Test and Quality Center enables the Automation Engineer to effectively maintain the resources and settings, while enabling Subject Matter Experts to implement business process tests.

Business Process Testing uses a keyword-driven methodology for testing, based on the creation and implementation of business components and business process tests. A business component is an easily-maintained, reusable unit comprising one or more steps that perform a specific task within an application. A business process test comprises a series of business components, which together test a specific scenario or business process. For example, for a Web-based application, a business process test might contain five components—one for logging on to the application, another for navigating to specific pages, a third for entering data and selecting options in each of these pages, a fourth for submitting a form, and a fifth component for logging off of the application. Business components and business process tests are generally created inQuality Center by Subject Matter Experts, although Automation Engineers can also create business components in Quick Test.

Components in QTP

QuickTest enables you to create and modify two types of components: business components and scripted components. A business component is an easily-maintained, reusable unit comprising one or more steps that perform a specific task. A scripted component is an automated component that can contain programming logic. Scripted components share functionality with both test actions and business components.

Automation Engineer:

The Automation Engineer is an expert in using an automated testing tool, such as QuickTest Professional. The Automation Engineer works with the Subject Matter Expert to identify the resources that are needed for the various business process tests.

The Automation Engineer then prepares the resources and settings required for testing the features associated with each specific component, and stores them in an application area within the same Quality Center project used by the Subject Matter Experts who create and run the business process tests for the specific application.

Each application area serves as a single entity in which to store all of the resources and settings required for a component, providing a single point of maintenance for all elements associated with the testing of a specific part of an application. Application areas generally include one or more shared object repositories, a list of keywords that are available for use with a component, function libraries containing automated functions (operations), recovery scenarios for failed steps, and other resources and settings that are needed for a component to run correctly. Components are linked to the resources and settings in the application area. Therefore, when changes are made in the application area, all associated components are automatically updated.

The Automation Engineer uses Quick Test features and functionality to create these resources from within Quick Test. For example, in Quick Test, the Automation Engineer can create and populate various object repositories with test objects that represent the different objects in the application being tested, even before the application is fully developed. The Automation Engineer can then add repository parameters, and so forth, as needed. The Automation Engineer can manage the various object repositories using the Object Repository Manager, and merge repositories using the Object Repository Merge Tool. Automation Engineers can also use Quick Test to create and debug function libraries containing functions that use programming logic to encapsulate the steps needed

HP Business Process Testing Terminology:

Application Area:

A collection of resources and settings that are used for the creation and implementation of business components. These include function libraries, shared object repositories, keywords, testing preferences, and other testing resources, such as recovery scenarios. An application area provides a single point of maintenance for all elements associated with the testing of a specific part of your application. You can define separate application areas for each part of your application and then associate your components with the appropriate application areas.

Business Component (or Component):

An easily-maintained, reusable unit comprising one or more steps that perform a specific task. Business components may require input values from an external source or from other components, and they can return output values to other components.

Also known as Keyword-Driven Component

Manual Component:

A non-automated business component created in Quality Center. In QuickTest, you can view and work with manual components only after converting them to automated business components.

Scripted Component:

An automated component that can contain programming logic and can be edited in QuickTest using the Keyword View, the Expert View, and other QuickTest tools and options

Keyword View:

A spreadsheet-like view that enables tests and components to be created, viewed, and debugged using a keyword-driven, modular, table format.

Function Library:

A document containing VBScript functions, subroutines, modules, and so forth. These functions can be used as operations (keywords) in components. You can create and debug function library documents using the QuickTest function library editor.

Business Process Test:

A scenario comprising a serial flow of business components, designed to test a specific business process of an application.

Component Input Parameters:

Variable values that a business component can receive and use as the values for specific, parameterized steps in the component.

Component Output Parameters:

Values that a business component can return. These values can be viewed in the business process test results and can also be used as input for a component that is used later in the test.

Local Input Parameters:

Variable values defined within a component. These values can be received and used by a later parameterized step in the same component

Local Output Parameters:

Values that an operation or a component step can return for use within the same component. These values can be viewed in the business process test results and can also be used as input for a later step in the component.

Roles:

The various types of users who are involved in Business Process Testing

Automation Engineer:

An expert in QuickTest Professional automated testing. The Automation Engineer defines and manages the resources that are needed to create and work with business components. The Automation Engineer creates application areas that specify all of the resources and settings needed to enable Subject Matter Experts to create business components and business process tests in Quality Center. The Automation Engineer can create and modify function libraries, and populate a shared object repository with test objects that represent the different objects in the application being tested. The Automation Engineer can also create and debug business components in QuickTest.

Subject Matter Expert:

A person who has specific knowledge of the application logic, a high-level understanding of the entire system, and a detailed understanding of the individual elements and tasks that are fundamental to the application being tested. The Subject Matter Expert uses Quality Center to create and run components and business process tests.

SAP TAO FAQ's

What is SAP TAO?
Which Version you are using?
What is the Latest Version in SAP TAO?
What are the Advantages in SAP TAO?
What are the Patches required for SAP TAO?
What is BPT?
Difference between BPT & SAP TAO?
Which Framework using for SAP TAO?
What is CBASE?
What is the SAP TAO Architecture?
What are the Prerequisites for SAP TAO?
SAP Solution Manager Mandatory for SAP TAO 1.0?
SAP Solution Manager Mandatory for SAP TAO 2.X?
What is UI Scanner?
What is Inspector?
How many ways to Create a components using TAO 1.0?
How many ways to Create a components using TAO 2.x?
Which service pack required for SAP TAO 2.7?
What is Import/Export?
What is Consolidate?
What is PFA?
What is Change Analyzer?
What is a Component?

HP BPT FAQ's

What is BPT?
How many ways to create a Component using BPT?
What is Application Area?
What is Keyword Driven Components?
What is Scripted Component?
What is BPT Architecture?
How to passing values?
How to grouping the Components?
What are the disadvantages for BPT?
How to Iterate the components?

About SAP TAO

or when the system generates any return values (i.e., Sales order number).

Develop m0odular based components for repeatable processes to optimize the maintenance phase.

Never use a Transaction Code as a parameter.

Use test statuses (i.e., pass, fail, run required, etc.) appropriately within Quality Center to properly define the status of a given artifact to determine its true state.

Create custom component templates for users to add details to automated test scripts.

Create Excel templates with login information to support external data.

SAP Automation Testing

Tuesday, December 18, 2012

QTP Important Study Links

Tuesday, December 11, 2012

SAP Automation by Sandip.G

Business Process Testing with QTP by Sandip.G

CRM Click WebButton

Wednesday, October 3, 2012

Order to Cash Cycle -Flow

Wednesday, July 11, 2012

About HP BPT

HP Business Process Testing

HP Business Process Testing

Understand Business Process Testing

Components in QTP

HP Business Process Testing Terminology:

SAP TAO FAQ's

About SAP TAO

About Automation:

SAP Test Acceleration & Optimization:

SAP TAO Features:

SAP TAO Features

Framework Architecture:

Driver Script / Test Cases:

Common Functions:

Data Load Components:

Data Management Solution:

Reporting:

Component Folder Structure:

SAP Transaction Components:

SAP Common Functions:

Actions:

GUI Functions:

Verification's:

Steps for Script Development:

SAP TAO Best Practices Recommendations:

Best Practices for Customizing: