About Me

Professional History and Credentials

I have been involved in Software Testing as Software Test Engineer from past few years, and have tested a number of software applications on a variety of platforms. I have also been involved in some form of automated testing or another during this period.

At SGS Infotech, I was involved in testing Geographical Information System (GIS) applications written in ASP. Here I tested the “PROGis”, which was allow to view the acquired Land record of "Taj Expressway, Noida" using the different-2 maps (using Archview). I was also involved in testing the Enterprise Resource Planning (ERP) application written in Java. I tested the “JOfficeDesk”, which allowed to automate the complete SGS Infotech.

During my employment at Orion India I successfully implemented Testing Team. I was in charge of testing Complete Garment ERP AMTPlus. I tested the Complete ERP System there. You can get the summary on www.obsllc.com . I have played a good role of Team Lead there. Now lot of Garment players are using this system in US like SLFashion, Apollo Garments etc.

During my employment at WNS IT Services I successfully Tested Mortgage Banking application Risk Management DB (RMD)of First Magnus Finance Corporation, USA.

Current I am working with MNC as a Testing Architect.

KR TESTING SOLUTIONS

KR Testing Solutions is an independent quality assurance and testing Organisation. Founded in 2006. We provide comprehensive software testing services and solutions for all testing needs. Our goal is to provide the better quality product to our clients.

KR Testing Solutions delivers effective, customized solutions for clients in a wide array of industries and technologies, and at significant cost savings. We have the expertise to perform functional testing of applications, performance, load and stress testing of web sites, and automation of regression tests. In addition, we will check sites for browser compatibility and accessibility compliance.

I hope that you will give me a chance for providing a better solutions of your problems.

Go to KR Testing Solutions

SOA(Service Oriented Architecture) Testing

SOA Testing

---

KR Testing Solutions offers testing Services in Service Oriented Architecture (SOA), Cloud Computing and Virtualization environment. Testing-WHIZ's comprehensive tool-based, message-driven test approach for SOA testing facilitates application-to-application communication across multiple layers of the technology stack.  KR Testing Solutions addresses SOA challenges, security issues, and governance to help you achieve a robust system implementation.

Challenges in SOA Testing

Since SOA applications are composed of loosely coupled, business level services, distributed over the network, following are the testing challenges:

• Data Driven Testing (No GUI)
• Difficulty in isolating the bugs due to presence of multiple layers
• Difficult to test Secure Web Services; especially those requiring encrypted and signed test data
• Lack of effective reporting and debugging capabilities in available tools, that is essential for Web Services
• Increased number of integration and interoperability because of multiple service involvement and communication among them
• Involvement of 3rd party services in end-to-end solution
• Different services may have different authorization / authentication approach
• Performance testing problems due to:
  • Small service large overhead
  • Service need specific hardware specification
  • Distributed service may have network latency

KR Testing Solutions offers the four major aspects of comprehensively testing a Web Service: Functionality, Security, Performance and Conformance:

• WSDL Verification (Schema / XML Validation)
• Performance Testing of applications on Cloud Environment
• Validation of data / application migration from standalone application server to Cloud Environment
• Testing of load balancing functionality in Cloud Environment
• Multi-vendor storage Compatibility Testing (Disks and Drivers)
• Testing Data Center Inventory Management Applications
• Conformance (W3C and WS-I Standards) and Interoperability Testing

Tutorial 1 - What is QTP?

This tutorial introduces Quick Test Professional , features of QTP as Functional Automation Tool & the concept of ADD-ins




Summary

* Quick Test Professional , popularly know by its acronym QTP is the flagship functional automation testing tool from Mercury Interactive now acquired by HP
* It is an icon based tool, which automates the functional & regression testing of an application
* QTP is easier to use and implement for both technical & non technical testers in comparison to other functional testing tools available.
* Quick Test is the market leader in Functional Automation Tool with over 50% market share
* QTP's Scripting Language is VB Script which is easy to use , understand and program
* Quick Test Professional enables Business Process Testing (BPT)
Supports large pool of software development environments like SAP , Web , Oracle etc.
* The trainings have been recorded using QTP version 9.5 but you may use any higher or lower versions for your learning purposes
* For All Hands On in these trainings, we will be using “Flight Reservation” Application which comes bundled with QTP

Tutorial 2 - First Look Flight Reservation Application

This tutorial introduces Flight Reservation Application which will be used for hands-on for the rest of the tutorials.



Notes:
* Flight Reservation Application comes pre-installed with QTP
* Using Flight Reservation , you can book a flight between two cities, even modify or delete and exisiting booking.
* You may also fax a booking to a customer with your custom signature.
* Flight Reservation has a Reports and Graphs section which helps analyze the ticket selling trends.
* A small number of bookings is pre-populated for any new agent , so that you do not have to create test data.
* The application has been designed to help learn all the features provided by QTP. At times , you may find this application buggy but your focus should not be technical accuracy of the application, but on its use as a tool, to learn various features of QTP.

Tutorial 3 - First Look QTP IDE

This tutorial introduces the Quick Test Professional IDE



Video Transcript with Key Takeaways highlighted

* Without further ado , Lets look into QTP
* To launch QTP, In Start Menu, Choose Programs > Quick Test Professional Folder > Quick Test Professional
* The first time you start QTP, the Add-in Manager dialog box opens.It Displays list of all installed add-in along with license expiry date.
* It is recommended you select only the add-ins required for your particular testing session . Because at times , different add-in interfere with each other degrading object identification and QTP's performance. QTP will remember the add-ins you load so that the next time you open QTP the add-ins you selected in the previous session are selected by default.Also, If you do not want this dialog box to open the next time you start QTP clear the Show on startup check box.Click OK.
* The Start Page describes the new features in this release—including links to more information about these features.It also provides links to Process Guidance, a tool that offers best practices for working with QTP.You can open a document from the list of Recently Used Files,or you can click the buttons in the Welcome! area to open new or existing documents.If you do not want QTP to display the Start Page when you next open QTP ,select the "Don’t show the Start Page window on startup" check box.When you select this option, the Start Page is also automatically hidden for the current QTP session as soon as you open another QTP document.To display the Start Page again, select View > Start.
* Title Bar Displays the name of the active document. If changes have been made since it was last saved, an asterisk (*) is displayed next to the document name in the title bar.
* Menu Bar Displays menus of QTP commands.
Toolbars Contains buttons to assist you in managing your document
Document Tabs Enables you to navigate open documents
* Keyword View Displays test steps in a graphical representation
* Expert View Displays test steps as a VB Script line.
* Active Screen Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.
* Data Table Assists you to parametrize your test.
Test Flow Displays the hierarchy of actions and action calls in the current test, and shows the order in which they are run.
* Below are Tabs For Other Panes.
* You can change the look and feel of the main QTP window, as required
* In the QTP window, select View > Window Theme, and then select the way the window should appear from the list of available themes.
* You can move the QTP window panes to suit your own personal preferences.Say we want to Move the Test Flow Pane .In the QTP window, drag the title bar of the Test Flow Pane.As you drag the pane, markers are displayed in the active pane and on each edge of the QTP window.Drag the Test Flow and hold the cursor over the various markers.A shaded area is displayed, indicating the new location of the pane.Lets move it to Right. Release the mouse button.The Test Flow Pane snaps into place and is displayed as a new pane in the shaded area.
That’s all to the QTP IDE

Tutorial 4 - HP Quick Test Professional

This tutorial identifies the TEST STEPS that need to be automated for your First Test Script using QTP



Video Transcript with Key Takeaways highlighted

* Now, Lets Record Our First Script.For Our Application Under Test i.e. Flight Reservation - lets validate a simple test scenario out of possible many
The Scenario Would Be"Check that user successfully logs in to the application on inputting valid Agent Name & Password"
Test Steps required to validate this scenario would be
Step 1) Open Flight Reservation Application
Step 2) Enter Valid Agent Name
Step 3) Enter Valid Password
Step 4) Press Ok
Step 5) Close Application After Successful Login.
Lets automate these 5 steps in QTP

Tutorial 5 - Record and Run Settings QTP

This tutorial introduces the Record & Run settings & It demonstrates , how to record a script in QTP



Video Transcript with Key Takeaways highlighted

* In QTP click the record button.The Record and Run settings Dialog Box Opens.This box opens automatically each time you begin recording a new test.
Record & Run settings shows a tabs corresponding to add-ins installed and loaded for your test.So, for example if you have SAP Add-in Installed and loaded you will see a SAP tab.
The Windows Application tab is always available and be used for environments, such as Visual Basic, ActiveX, and terminal emulators.
* For any Environment, the Record and Run settings can be classified into two generic groups
1) Record & Run on ANY window belonging to that particular environment
2) Record & Run on a SPECIFIC window belonging to that particular environment - which is the recommended Option
For the time being , lets stick to default settings .Once settings are done , QTP remembers and uses the same settings for additional record sessions on the same test, unless you manually open the Record and Run Settings dialog box to modify the settings.
Click okay
* QTP Starts Recoding Mode
Step # 1 is to Open Flight Reservation Application
Click Start Menu > Program Files > Quick Test Professional > Sample Applications > Flight Reservation
Step # 2 Enter a Valid Agent Name greater than 4 characters say Guru
Step # 3 Enter a Valid Password which is by default MERCURY
Step # 4 Click Okay
Step # 5 Check that the Flight Reservation opens successfully which it is . Click the close button.
* All the 5 steps are now recorded
In QTP , Stop recording
* Save the script as "LogIn"

Tutorial 6 - All about Object Identification

This tutorial demonstrates how QTP identifies an on - screen GUI Object and the concept of QTP's Test Object Model



Video Transcript with Key Takeaways highlighted

* QTP also uses a "human" like technology for object identification
* During Record Time QTP tries to learn properties of a GUI object on which operation is performed.
* During Run-Time QTP compares the stored object properties with actual properties of object available on screen and uniquely identifies an object independent of its location on screen
* The stored object and together with its properties is called TEST Object
* During Run-Time, the actual object available on the application under test is called Run-Time Object
* This is Quick Tests "Test Object Model"
* Information about the Test Objects is stored in Object Repository
* Add-ins help in instructing Quick Test

Tutorial 7 - Expert View in QTP

This tutorial interprets the Expert View and gives its Syntax




Video Transcript with Key Takeaways highlighted

* In the Expert View , each line represents a Test Step in VB Script
* To understand expert view better , lets analyze Step # 2 from our TEST recorded earlier
* An Object's Name is displayed in parentheses following the Object Type.Here the Object Name is Login and * Object Type is Dialog
* Objects in Object Hierarchy are separated by a "dot".Here Dialog and WinEdit are fall in the same Object Hierarchy
* Just to put things in perspective, Object Hierarchy is Object Oriented Concept where set of objects that are grouped together in a parent-child relationship.In our case Dialog Box is the Parent Object and WinEdit is the Child Object
* The Operation performed on the object is always displayed at the end of the statement followed by any values associated with the operation.Here the word "Guru" is inserted in the AgentName Edit Box using the Set Method
* Syntax for a statement in expert view is GUI object on which the operation is performed along with its complete hierarchy followed by the Operation on the Object and value associated with that Operation

Tutorial 8 - Compare Keyword view and Export view in QTP

This tutorial interprets the Keyword View and compares the Expert & Keyword View




Video Transcript with Key Takeaways highlighted

* The Keyword View is comprised of a table-like view where
* Each step is a separate row in the table and
* Each column represents different parts of the steps.
* Item Column contains the item on which you want to perform the step. This column uses icons displays the hierarchy of the GUI object on which operation is performed
* Operation Column contains the operation to be performed on the item.
* Value Column contains the argument values for the selected operation,
* QTP automatically documents each step for easy understanding in the Documentation Column
* These 4 columns are default but you can also use assignment & comment columns in Keyword View
* That’s all to the Keyword View
* Lets Compare the Keyword and Expert View using Step no 2 from our script. You will observe that the same object hierarchy is displayed in both Expert & Keyword Views and they map to the same operation and argument value.
* Essentially , Keyword & Expert view contain the same data but arranged in different format.
* In fact you can perform all operations like create , modifying a step . using the Keyword View but to gain mastery over the tool we will restrict ourselves to the Expert View

Tutorial 9 - QTP

This tutorial interprets the script that was recorded in earlier tutorials




Video Transcript with Key Takeaways highlighted

* Now , Lets go ahead and understand our recorded test.
* The first step is the SystemUtil.Run Command which is used by default by QTP to open a application.So during recording , using the Windows Start Menu , when we finally navigated to the "Flight Reservation" application QTP identified the location of its executable file and inserted the System.Util Command to Open it.
* Step No 2 is Setting Agent Name as Guru as shown in the Active Screen
* Step no 3 is Pressing the Tab key on keyboard to bring Focus from Agent Name Field To Password Field , which is exactly this step. Human users need to use tab or click operations to focus on a particular object on screen.. On the other hand , QTP can directly identify an object using object properties and does not required these "maneuvering" operations. We can delete this step , as QTP will still be able to set the password field without this operation
* Next Step is Setting the Password as Mercury. QTP automatically encrypts passwords entered while recording to avoid security breaches. This value can not be decrypted ie. There is no way to recover the original value using this cryptic data. You can explicitly encrypt a password using the Password Encoder Tool. For our learning purposes , we will use the password in its raw form. And the operation will also change to Set
* Next Step is clicking the okay button
* Next Step is closing the application after successful log on
* So the 5 steps mentioned in our test script are recorded in QTP

Tutorial 10 - What is Replay in QTP?

This tutorial introduces the concept of REPLAY . It demonstrates the Run Settings available in Quick Test



Video Transcript with Key Takeaways highlighted

* Now , lets go ahead and REPLAY the script to ensure the test steps have recorded correctly.
* Click the Run Button.
* The Run Dialog Box Opens which enables you to specify the location in which you want to save the run session results.
* This option displays the default path and folder name in which results are stored. By default results are stored in Test Folder .A new sub-folder is created with the name RESn .The number n is incremented for each run.
* You may accept the default settings or specify a folder of your choice
* Temporary run results folder options saves the run results in a temporary folder. This option overwrites any results previously saved in this folder.
* Its recommended that while developing your test script choose the Temporary option and once the script is baseline you can use the new folder option
* In our case we will use the temporary option and click okay. QTP enters the run mode
and will start executing steps one by one.
* In QTP window you can see a yellow marker pointing at the step which is currently being executed.
* During Replay the script performed exactly the same 5 steps that were recorded which signifies that there were no errors in recording.
* Test Results are also shown

Tutorial 11 - Test Results in QTP

This tutorial demonstrates the various features available in the Test Results generated by QTP



Video Transcript with Key Takeaways highlighted

* Lets understand the Test Results generated by QTP
* Right Hand Side shows Test Results Summary
* Left Hand Side is Test Results Tree - an icon-based view of the test steps that were performed while the test was running. Similar to the test tree in Keyword View
* If you select a step in the tree , the right panel gives it complete details
* This Apart
* You can capture Movie / Screenshots of entire Test Run using Tools > Options > Run Tab
* In our case this movie was recorded and , screen shots were captured
* You can print/export full/part of results in HTML , Word or PDF format.
* You can exports the results to Quality Center
* You can change the format of Results by using Results.xml and creating a XSL

Tutorial 12 - All about parameters in QTP

This tutorial demonstrates parameterization



Video Transcript with Key Takeaways highlighted

* You may be wondering why take the Herculean effort to automate this simple scenario
* Check that user successfully logs in to the application on inputting valid Agent Name & Password
* The need becomes obvious if we extend the scope of the scenario to include a Combination of valid ALPHANUMERIC Agent Name & Password
* In this case , the Test Steps Will Remain the Same. But we will have more combinations of Data To TEST. We will restrict to just 3 of possible 8 combinations
* To achieve this you can either copy the six steps and give different data values which is in fact * something you would do manually. Or you can use Parameterization
* The easiest way to parameterize an argument , in our case Guru is in Keyword view , Click the Parameterization Icon
* Value Configuration Dialog Box Opens. Currently the value is set to a Constant. Click on Parameter Radio Button. QTP assigns a default name to these parameter. You can give a name of your choice. Click Okay
* In the Global Sheet , a column with Header "Agent Name" and value Guru is created. You can enter more values for this parameter
* Likewise you can also parameterize the argument Password and enter different test data sets.
* What this Data sheet means is QTP will iterate the same 6 steps that we have recorded 3 times. During * first iteration it will use the data in the first row. During second it will use data in the second row and so on
* Now lets run the script. This is the first iteration. This is the second iteration
* In the status bar QTP gives information of the row, it is currently using as test data and highlights the * corresponding row in the data sheet. The results will show summary of the 3 iterations.
* A brief recap of parameterization
* Parameterization allows us to pick different values at run time.
* It Reduces Time and Effort.
* Usage of Data Drivers allow us to use the same data for various input boxes. Data Drivers is feature provided by QTP which shows all the constants that could be parameterized in one single window

Tutorial 13 - What are the standard checkpoints in QTP?

This tutorial introduces Checkpoints



Video Transcript with Key Takeaways highlighted

* You may have notice that results generated for our test script has no Pass/ Fail Status without which our automation is incomplete
* The expected TEST RESULT for our scenario should be - Flight Reservation Window
* which is this screen should appear after entering valid username and password. To accomplish this we will need to record an additional step # 6 which is Check Flight Reservation Window is Displayed..
* Automation of this verification step can be achieved using Checkpoints- A checkpoint is a verification point that compares the current value with the expected value for specified properties of an Object. If they current and expected value match it generates a PASS status otherwise FAIL status
* Lets go ahead and record step # 6
* To add a checkpoint , right click on the step # 5 after which checkpoint needs to be inserted .Choose Insert Standard Checkpoint. Checkpoint Properties Dialog Box Opens.
* QTP assigns a default name to checkpoint. You can input your preferred name
* The table shows all the recorded properties and their corresponding values for the object. The Selection mark indicates that these properties will be checked
* ABC icon indicated that the property values are a constant. If you parameterize any of the selected properties the icon changes correspondingly
* Lets stick to the default and insert the statement after the current step. Click okay
* A check statement with checkpoint name is inserted at line # 6.Lets replay the script
* The script gives a Run-Time Error
Well this is a common source of error for beginners and happens because at step # 5 , QTP closes the Flight * Reservation Screen and when the execution reaches step # 6 there is no Flight Reservation Screen Object available to very its properties. You need to ensure , that the object which are verifying is available while QTP executes the Checkpoint Step
* This error can be rectified by changing the sequence of Tests Steps. You need to switch
* Step 5 & step 6 . In the new scenario step 5 is verify the Flight Reservation Window Exists and step 6 is to Close the application
* In QTP , you just need to cut step # 6 and paste it at location of step # 5.Lets replay the script again. * The Script passes and the results tree gives the checkpoint values that were compared. That's all to standard checkpoints
* A recap of checkpoints-
* There are many types of checkpoints and the most generic is the standard checkpoint.
* Standard checkpoints compare the expected values of object properties captured during recording to the object's current values during a run session

Tutorial 14 - Types of checkpoints in QTP

This tutorial demonstrates different types of Checkpoints in Quick Test Professional




points to remember

A Checkpoint is a confirmation or verification point in which the value of some property which is expected at a particular step is compared with the actual value which is displayed in the application. Based on the expected values Checkpoints are classified as follows

* Page Checkpoint : A Standard Checkpoint created for a web page can be called a Page Checkpoint. It is used to check total number of links & images on a web page. Page Checkpoints can be used to check Load Time i.e. time taken to load a web page.
Bitmap Checkpoint helps a user in checking the bitmap of an image or a full web page. It does a pixel by pixel comparison between actual and expected images.
* Image Checkpoint enable you to check properties like source file location of a web image. Unlike , Bitmap Checkpoint you can not check pixels(bitmaps) using image checkpoint.
* Text Checkpoint is Used to check expected text in a web-page or application. This text could be from a specific region of the application or a small portion of text displayed
* Accessibility Checkpoints verifies compliance with World Wide Web Consortium (W3C) instructions and guidelines for * Web-based technology and information systems. These Guidelines make it easy for disabled to access the web.
* Database Checkpoints create a query during record time and database values are stored as expected values. Same query is executed during run time and actual & expected values are compared.
In Table Checkpoint , you dynamically can check the contents of cells of a table (grid) appearing in your * environment. You can also check various table properties like row height , cell width and so on. Table Checkpoint is similar to Database Checkpoint
* Using XML Checkpoints you can verify XML Data ,XML Schema, XML Data

Tutorial 15 - How to insert output values in QTP?

This tutorial demonstrates the concept of Output values in Quick Test Professional



points to remember

An output value step ,is a step in which a object property value is captured at a specific point in your test and stored at a desired location. The stored values can be used as input at a different points in test script. Multiple properties of an object can be selected and outputted.

Types of Output Values

* Standard output value
* Text /Text Area output value
* Data base output value
* Xml output value (from application/resources)

Tutorial 16 - Conditional Loops in QTP

This tutorial demonstrates advanced coding in QTP using if and else loop



Video Transcript with Key Takeaways highlighted

* From your testing background you will certainly infer that a more accurate Test scenario would be * Validate the Login Functionality of Flight Reservation which should have two sub scenarios
* Check that user successfully logs in to the application on inputting a COMBINATION OF valid ALPHANUMERIC Agent Name & Password
* Check that user log on fails on inputting INVALID Agent Name & Password
* More so , a robut automation script should be able to accept and handle both valid and invalid login details
* We have the sub-scenarios already recorded So the challenge is to integrate them.
* You May observe for both the scripts - STEPS ,Launch Flight Reservation Application, Enter Agent Name ,Enter Password ,Click OK ,while steps Checkpoint ,,Close Flight Reservation Window, for positive scenario, and steps ,Output Error Information ,Close Error Info Window ,Close Login Dialog Box, for negative scenario are different
* There are many ways to integrate them and once of the ways ,is to use if and else loop and check whether error information screen exists after entering the agent name and password. if yes do the steps for negative scenario, if no do the steps for positive scenario
* In QTP Window, After step # 4,Add a step if else loop, The check condition is whether error information screen exists. Copy this step and paste it as check condition.
* Delete the Click Operation. And replace it with Exists method. This method is applicable to almost all objects and checks whether the particular objects exists on screen or not
* If result is true do the negative scenario steps. I will cut and paste the steps inside the loop
* Copy the steps from the positive scenario and paste it in the else loop. Lets run the test for one valid and one invalid login credentials. The test Runs successfully .Note is you saved the tests in the order mentioned in the tutorials
* PositiveLogon to NegativeLogon and Negative Logon to Combined you should have no problem running the test.
* Apart from if and else you can also use - if elseif., while wend.,do case ,for Loops. as per your requirements

Tutorial 17 - How to user Report.Report Event in QTP

This tutorial demonstrates the use of function Reporter.Report Event and Results Formatting.The tutorial will ask you to develop a script. To maximise your learning , please do complete the scripting exercise.



points to remember about QTPs Test Results Formatting

* You can use Reporter.ReportEvent to report custom test steps in QTP's test results tree
Syntax -Reporter.ReportEvent EventStatus, ReportStepName, Details [, ImageFilePath]
* Event Status can have values
* 0 or micPass sends a pass status to test result window
* 1 or micFail sends a pass status to test result window
* 2 or micDone sends a message to test result window without affecting the Pass/Fail status
* 3 or micWarning sends a warning message to the result window
* When test cases are executed using automation tools it may be difficult for certain users to understand the test results You can use results.xml to create an xsl which will present the test results as per your preferences
* You can use VBScript Library functions to store the results in xls or a text file.

Tutorial 18 - Complete Guide on Actions in QTP

This tutorial demonstrates Actions. It uses the vanilla Test Script created in previous tutorials with 5 steps to log in into Flight Reservation.This tutorial is the longest in all QTP tutorials and its recommended you take notes while viewing it.



key takeaways:

* Actions help divide your test into logical units or Business Processes
* Actions help create a script which is more modular and efficient.
* When a script is newly created it consists of only one action .A script can consist of one or more Actions .
* There two types of Actions 1)Reusable Actions & 2) Non-Reusable Actions
* Reusable Action can be used in other Tests. They can be used in the same Test Script multiple times.
* Non reusable Action can not be used in other Tests. They can be called in the same script only once
* You can split an existing action in two ways 1) Independent of each other which splits the selected action into two sibling actions 2) Nested Action which splits the selected action into a parent action whose last step calls the second, child action
Q* TP provides 2 type of datasheets 1) Global & 2) Local
* GLOBAL Datasheet : It is Unique for the entire test. Any Action can access and write data into Global Datasheet. Sheet is named “GLOBAL”
* LOCAL Datasheet : Equal to number of Actions in the sheet. An Action can read and write data into its own local Datasheet only. Sheet name = “ACTION NAME”
* There are two methods to import Actions into a Test 1) Call to Copy & 2) Call to Existing.
* Call to COPY of an Action : When you make a Copy of an Action , the action is copied in its entirety, including checkpoints, parameterization, and the corresponding action tab in the Data Table into the calling test . When you insert a copy of an existing action, you can make changes to the copied action, and your changes will not affect nor be affected by any other test. You can insert copies of both reusable and non-reusable actions
* Call to an EXISTING Action : Calls to actions are read-only in the calling test. They can only be modified in the test in which they were created. Enables you to use the same action in several tests and makes it easy to maintain tests. You can make calls to only “Reusable” actions.
* You can change the action iteration frequency by selecting Action Call Properties > Run Tab