Appperfect Web Test 426f3e

.link" is created in <ECLIPSE_HOME>\links folder. Integration with Eclipse Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within Eclipse: 1. AppPerfect menu-item will be added within the Eclipse toolbar. Click it to launch any of the AppPerfect products. 2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect products will be available as part of the IDE once started.

NetBeans 4.0, 4.1 and 5.0 Plugin Installation When you select the option to integrate AppPerfect with NetBeans the following steps are taken: 1. The plugins jars are placed in NETBEANS_HOME\ide \modules folder. 2. The other required jars are placed in the NETBEANS_HOME\ide \modules\ext folder. 3. The config file "com-appperfect- .xml" is placed in the NETBEANS_HOME \ide \config\Modules folder. Integration with NetBeans Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within NetBeans: 1. AppPerfect menu-item will be added within the NetBeans toolbar. Click it to launch any of the AppPerfect products.

2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect product will start a new instance after gathering available details from the IDE.

IntelliJ Idea 3.0, 4.x, 5.0 and 5.1 Plugin Installation When you select the option to integrate AppPerfect with IntelliJ Idea, the following steps are taken: 1. A folder named 'AppPerfect' is created in IDEA_HOME\plugins. 2. The plugins jar and other required jars are placed in the IDEA_HOME\plugins\appperfect folder. Integration with IntelliJ Idea Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within IntelliJ Idea: 1. AppPerfect menu-item will be added within the IntelliJ toolbar. Click it to launch any of the AppPerfect products. 2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect product will start a new instance after gathering available details from the IDE.

JBuilder 9 Personal, JBuilder X Foundation, JBuilder X Enterprise Edition Plugin Installation When you select the option to integrate AppPerfect with JBuilder, the following steps are taken: Step 1: The plugins jar and other required jars are placed in the JBUILDER_HOME\lib\ext folder. Integration with JBuilder Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within JBuilder: 1. AppPerfect menu-item will be added within the JBuilder toolbar. Click it to launch any of the AppPerfect products.

2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect product will start a new instance after gathering available details from the IDE.

JDeveloper 10g Plugin Installation When you select the option to integrate AppPerfect with JDeveloper, the following steps are taken: Step 1: The plugins jar and other required jars are placed in the JDEVELOPER_HOME\lib\ext folder. Integration with JDeveloper Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within JDeveloper: 1. AppPerfect menu-item will be added within the JDeveloper toolbar. Click it to launch any of the AppPerfect products. 2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect product will start a new instance after gathering available details from the IDE.

IBM WebSphere Studio 5.1.x Plugin Installation 1. A link file "com.appperfect. .link" is created in <ECLIPSE_HOME>\links folder. Integration with WebSphere Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within WebSphere: 1. AppPerfect menu-item will be added within the WebSphere toolbar. Click it to launch any of the AppPerfect products. 2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect products will be available as part of the IDE once started.

IBM Rational Application Developer 6.0 Plugin Installation 1. A link file "com.appperfect. .link" is created in <ECLIPSE_HOME>\links folder. Integration with WebSphere Once the IDE integration has taken place, you will be able to access the AppPerfect menu in the following ways within WebSphere: 1. AppPerfect menu-item will be added within the WebSphere toolbar. Click it to launch any of the AppPerfect products. 2. AppPerfect products can also be accessed through context-sensitive pop-up menus. AppPerfect products will be available as part of the IDE once started.

UI Reference This chapter gives an overview of the various components in the UI of AppPerfect Web Test. In the AppPerfect Web Test project area there are two panes: the left hand navigational frame and the right hand frame that holds the for the selection made on the navigational frame. The right frame gives the details of the selection on the left frame. For example, consider that the Editor Tab has been selected on the left frame. The right frame will show the General Settings and Attribute Settings for the element selected on the tree. There are two tabs shown in the left navigational frame: Editor Tab The left hand navigational frame shows the Editor tab with the test tree as soon as the recording is over. When a test has been recorded, selecting an element on the test tree makes the right frame to show the for settings for the element selected on the test tree. The test tree has a root node that is name of the test and one or many group nodes that represent the different groups in the test. The group node can have various types of node such as URL, sub-URL, event, and element. When the Test node, that is the parent node for the test tree, is selected the right frame shows the Project Settings and List of Groups in the test. When the Group node is selected on the test tree, the right frame shows the Group Settings and List of URLs in the group. When an URL is selected on the test tree, the right frame shows the General Settings and the Parameter Settings for that particular URL. When an event is selected on the test tree, the right frame shows the General Settings and the Attributes Settings for that particular event. When an element that is related to text such as a text area, text set, selected on the test tree, the right frame shows the General Settings, the Attributes Settings, and the Value Settings for that particular element. Results Tab Once a test is complete the reports generated for that test are shown in this tab. The Results tab on the navigational frame shows the reports tree. The Reports tab is not seen on the left frame when a new test is created or an existing test is opened. It can be seen only when a test is replayed. The Results tab is also seen when a test result file is opened using the Open Result option in the File menu.

Menu Items ●

File Menu ❍

New... : Starts the new project wizard

❍

Open... : Opens an existing project

❍

Close : Closes the current project

❍

Save : Saves a project to the location where it was opened from or previously saved

❍

Save In TestManager... : Saves a project in TestManager.

❍

Rename... : Rename currently open project

❍

Result > Open... : Opens a existing result

❍

Result > Open from TestManager... : Opens a result from TestManager

❍

Result > Close : Closes the existing result being viewed

❍

Result > Save : Saves the result of the project in "results" folder

❍

Result > In TestManager... : Saves the result of the project in TestManager

❍

Result > Export Complete Result... : Export complete result to selected format

❍

●

●

❍

Print : Prints the selected result view

❍

Recent Project Files : Displays a list of recently created files

❍

Recent Result Files : Displays a list of recently accessed Result files

❍

Exit : Closes and exits the AppPerfect Web Test

Edit Menu ❍

Cut : Standard cut operation on selected node

❍

Copy : Standard copy operation on selected node

❍

Paste : Standard paste operation

❍

Delete : Delete the selected node

❍

Remove All : Remove all child nodes of the selected node

❍

Find : Find the node in the editor tree

❍

Add Group : Add new group to the editor tree

❍

Add Task : Add new task to the editor tree

Project Menu ❍

Run : Starts replaying a recorded test

❍

Run Selected : Starts replaying the selected groups

❍

Stop : Stops replaying the test

❍

Pause : Pauses the test

❍

Auto-update Test : Automatically update the test

❍

Auto-update Selected : Automatically update the selected groups

❍

Record a test... : Starts recording the test

❍

Import Groups Recorded : Import groups recorded from other projects

❍

Script Editor : Open Script Editor

❍

❍ ●

Send Result To... : Makes a zip file of the results of the current project and attaches it to a new email using the default email client

Properties.... : Opens the project properties wizard that allows to set/change the project properties Preferences... : Opens the common Web Test project wizard to set/change properties

Tools Menu ❍

Export Project As Command Line... : Export your Web Test project as Command

●

❍

line script file Export Project As ANT Script... : Export your Web Test project as ANT script

❍

Export view to : Export current view to various formats

❍

IDE Integration... : Opens the dialog box requesting selection of IDE to integrate with

❍

Options... : Opens the options wizard that is used to set system properties

Help Menu ❍

Table of Contents : Shows the entire help for the system

❍

Search : Shows the entire help for the system with the search tab selected

❍

Quick Help : Shows context sensitive help

❍

Technical : Takes you to the AppPerfect page on the Internet

❍

Forums : Takes you to the AppPerfect forums on the Internet

❍

About AppPerfect Web Test : Shows the information such as version, copyright related to AppPerfect Web Test

Toolbar Items ●

- Brings up the new test wizard for the creation of a project

●

- Opens existing project

●

- Saves current project

●

- Starts the test. All the test settings will be checked and if there are no errors then the test will start running

●

- Pauses the test temporarily and then can be restarted after some time

●

- Stops the test. This will stop a test and the required reports will be generated

●

- Launches the Browser recorder

●

- Opens the project properties wizard

●

- Opens the common Web Test project wizard

●

- Opens the options wizard that is used to set system properties

●

- Shows context sensitive help

Status Bar ● ● ●

●

View - Shows the edition of the AppPerfect Product: Evaluation, Standard or Professional. Status - Shows the status - Recording in Progress, Replaying in Progress or Reports Ready. Time - Shows time elapsed since recording started while recording is in progress. Shows time elapsed since replaying started when replaying is in progress. Date - Shows the current date and time.

AppPerfect Web Test FAQ 1. What are the key features of the AppPerfect Web Test? 2. What kinds of applications can be tested using AppPerfect Web Test? 3. What are the different types of errors that can be detected using AppPerfect Web Test? 4. How are parameters created and handled? 5. What are dynamic parameters? How do they work? 6. My dynamic menus are not being recorded and replayed. What do I do? 7. I want to run multiple iterations of my test, each with a different set of parameter values. How do I do that? 8. I want to check for certain value in one of the elements of the returned page to validate that the request was correctly processed. How do I add such validation? 9. I'm getting an error again and again. I've tried everything, but I'm stuck. What should I do? What are the key features of the AppPerfect Web Test? AppPerfect Web Test records all your actions in the Web browser and replays them at a later point without your intervention. AppPerfect Web Test is used for functional and regression testing on a continuous basis. What kinds of applications can be tested using AppPerfect Web Test? Most application that have a Web/html front end can be tested using AppPerfect Web Test. Commonly tested applications are based on Java/JSP/Servlet, ASP, PHP, AJAX . In addition, applications using Java applets and Macromedia Flash are also ed. What are the different types of errors that can be detected using AppPerfect Web Test? The following types of errors can be detected: 1. Whether the recorded test is replayed successfully. 2. Web Test detects any changes in the page content. (DOM Validation (Entire page validation)/ Element validation/ Text validation) 3. 4. 5. 6.

URL validation URL Parameter validation Event Validation (Whether the recorded events gets replayed or not) Iteration-wise reponse validation (You can use Parametratization to different set of values for each iteration)

How are parameters created and handled?

Most Web applications are dynamic in nature and work interactively with the 's data. data is communicated to the application by means of parameters. Parameters can either by ed via a URL or as part of the Http header of the request. AppPerfect provides extensive for defining and using parameters. Once a test is recorded, AppPerfect stores all parameters into the project as a property/value pair. Click on the "Parameters" node in the Editor to manage parameters. What are dynamic parameters? How do they work? A dynamic parameter is a parameter whose value is not know at test design time. An example of a dynamic parameter is a session ID. A unique session ID is generated once you to your server. AppPerfect s defining such dynamic parameter and tying its value to either a returned value in the http header or in the URL. My dynamic menus are not being recorded and replayed. What do I do? Most dynamic menus are implemented using the "MouseOver" event in JavaScript. By default, this event is NOT recorded. You must manually select recording this event by selecting Tools -> Options -> Web Test -> Auto Detect mouse-over events on elements having mouse-over event handlers. I want to run multiple iterations of my test, each with a different set of parameter values. How do I do that? These are the following ways in which you can access the Parameter Setting Wizard. ●

●

●

Select the URL node in the Editor tree and on right hand side Click the 'Parameters' tab. Here you can see the list of parameters that have been encountered while recording the task. Click a parameter name and then the button 'Parameterize'. You can also parameterize recorded attributes of element. Just select any element/event in the Editor tree and select Attributes tab on right hand side window and parameterize the Attribute using the "Parameterize" button provided. You can also parameterize arguments in event apis. Just select concerned event in the Editor tree and on right hand side Details tab look for Event arguments if any and parameterize the same using the "Parameterize" button provided. Say for example in case you need to run test with differnt input values for set/type events, then you can parameterize the "text" argument in this case.

On clicking 'Parameterize' button a parameter settings dialog will be shown, which will allow you to configure parameter value as constant or configurable test parameter. You can create new test parameter and associate it with URL Parameter/ Event argument/Attribute here. I want to check for certain value in one of the elements of the returned page to validate that the request was correctly processed. How do I add such validation? In the Editor view, click on the desired page. Click on the "Validation" tab. Add validation by

selecting the desired element in DOM tree. I'm getting an error again and again. I've tried everything, but I'm stuck. What should I do? ● ●

●

Close the currently opened project if it is open. Stop and close the application if it is running. Go to Tools ->Options-> Log Settings. Make sure the settings selected for all the products is: Debug (not Fatal). Open the project. Perform the operations that are giving you the error. The moment you get the error, stop all operations and send us the following files: 1. All files present in <WebTest_Home>\logs folder. 2. Project file i.e. *.adt file of that project. 3. Build number of the application. (Help->About AppPerfect...)

AppPerfect Scripting AppPerfect Software License Agreement Introduction Creating a Web Project Configuring a Database Configuring Test Parameters Creating Task Groups in Web Project Creating tasks in a Web task group Validating a task response

AppPerfect™ Web Test v 10.5.0 Scripting Guide

Copyright (C) 2002-2009 AppPerfect Corporation. All rights reserved. AppPerfect is a trademark of AppPerfect Corporation. Java is a trademark of Sun Microsystems, Inc.

Functional Testing an Web Application This tutorial provides a brief introduction to the AppPerfect Web Test product using a set of handson practice exercises. This tutorial assumes you have successfully ed and installed AppPerfect Web Test on your machine with the default options. Apart from this pre-requisite, this tutorial is self contained. This document is divided into following sections 1. Creating Project 2. AppPerfect Web Test Within each section, multiple exercises are listed. Each exercise forms a logical unit which is expected to take no more than a few minutes to perform. All exercises use the PetStore demo application running inside Apache Tomcat. The modified PetStore application and Tomcat are both bundled with this product. All exercises assume you have installed the product in C:\AppPerfect\WebTest folder and will be referred as WebTest_HOME henceforth in tutorial. If you have installed the product in some other folder, modify the instructions below appropriately. This tutorial is not intended as a comprehensive training guide. Please refer to the product documentation for detailed information. However, this tutorial will give you a very good overview of the products and substantially improve your productivity with the product.

Creating Project Exercise 1: Launch AppPerfect Web Test 1. Click on Start -> Programs ->AppPerfect Web Test x.x.x -> AppPerfect Web Test 2. On launching AppPerfect Web Test a Welcome page will be displayed. Go through the brief description given for product.

Exercise 2: Creating Project 1. Launch the Define New Project dialog by clicking File ->New... menu option. The New Project wizard will be launched. 2. Keep the default project name and location for the purpose of this exercise. We don't have to provide "Notification" settings. Click on the OK button. 3. A confirmation message saying that the project is saved will be displayed. Click on the OK button.

Now using this project we will create tests to demonstrate the functionalities of AppPerfect Web Test product.

AppPerfect Web Test NB:Please follow the steps provided in the "Creating Project" section to first create a project, then proceed further.

Exercise 1: Define a Web Test project 1. Once the common project is successfully created another dialog - Define Project Properties dialog - will be displayed. 2. The dialog shows various options which can be configured for the project, leave them default and click on OK button. 3. Click through all the menu items to familiarize yourself with the available features and how to access them. Viewing through all menu items will give a reasonable overview of the application. 4. Click Help -> Table of Contents menu item to see AppPerfect Web Test product documentation 5. Open the Preferences dialog by selecting the menu option Tools -> Options... 6. Review the default settings for Web Test and click the OK button to close the dialog.

Exercise 2: Recording a Test 1. Start tomcat server by selecting Start->Programs->AppPerfect Web Test x.x.x>Documentation and Examples->Examples->Tomcat running Petstore->Start Server. 2. To start recording, click on Project -> Record test... in the menu bar.' 3. 'AppPerfect Recorder' dialog will be displayed. Select the browser with which you need to record from the Browser drop down. Select ActionGroup1 from the Group combo. Provide starting URL as "http://localhost:8392/petstore". In the authentication drop down select "HTML Form based " and provide name: "j2ee" and :"j2ee". Now Click on 'Start recording' button. 4. An instance of selected browser will be launched with the PetStore home page loaded. Click on enter the store link. This will populate the database and display the PetStore main page. Note that populating the database might take some time. 5. Click on each link on the left: Birds, Reptiles, Dogs, Cats, Fish 6. Order an item by clicking on: Birds -> Amazon Parrot -> Adult Male Amazon Parrot -> Add to cart 7. Modify the quantity and click on Update Cart button. 8. Check out by clicking on the Check Out link. 9. At the 'Sign in' page, default values are already provided. Click on Submit. 10. Sign out of PetStore by clicking on Sign-out at top right of screen.

11. Close browser by clicking on File -> Close in the browser window. 12. Click on the Stop button of "AppPerfect Recorder" dialog to stop the recording session. 13. Click on Close button to close the 'AppPerfect Recorder' dialog. 14. In the AppPerfect Web Test window, look at the tree on the left. Each action you performed has been recorded. 15. Click on any of the recorded action on the left. The page associated with that action is displayed along with the actual element highlighted on the right hand side.

Exercise 3: Creating required parameters 1. In the editor tree, select 'Parameters' node. 2. On right hand side, click on 'Add Parameter' button to add a parameter. 3. In the 'Parameter Setting Dialog', enter 'sampleParam' as the parameter name. 4. Select 'Fixed Values' as Data Source. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.

Choose 'Sequential' as parameter selection. Under Add Value, enter 2 and click on the 'Add' button. Under Add Value, enter 3 and click on the 'Add' button. Click Ok. In the editor tree select the event which states something like (set on WebInputField 27:). In the details tab Click on the "text" argument in the Event Arguments table. Click on the 'parameterize' button. In the parameterization settings dialog, select "text" under the name column in the parameter settings table. 'Constant Value' will be selected with the value 27 in the text box. Select 'Parameterize' and from the combo box, select sampleParam. This will use the values of sampleParam as item quantity on each iteration. Click Ok. Now if the test is replayed for two iterations then each time different value will be picked for Item quantity.

Exercise 4: Adding page validations 1. Select the URL "Items" in the Editor tab. 2. Right click on the DOM Tree on the right and select the option 'Validate HTML source'. 3. This will validate all the elements & content of the web page when the test is replayed and report any validation error if there is any mismatch found in the recorded and replayed web page.

Exercise 5: Executing a test 1. Go to Project -> Properties.... menu to open Web Test project properties dialog. Change the

'No. of iterations' value to 2 and click OK. 2. To start replay of the recorded test, click on Project -> Run from the menu bar. 3. An instance of default browser configured at Tools -> Options -> Browsers is launched and each of the recorded events is replayed. No manual intervention is required during test replay, unless an error is encountered. 4. Note that two different values are picked for Item quantity for each iterations. 5. Stop running tomcat server by selecting Start->Programs->AppPerfect Web Testx.x.x>Documentation and Examples->Examples->Tomcat running Petstore->Stop Server.

Exercise 6: View and analyze results 1. After replay, results are displayed in Results tab. 2. Click on Results tab. Test results details are displayed on the right. Click on individual items in the tree on the left to view details on specific actions. 3. Browse and examine the different views that are displayed on selecting the various nodes in the navigation tree. 4. Select the ActionGroup node. This report gives a summary of the successful, failed, timedout & not played URLs & Events. 5. Select the URL Item and click on the Validation Results tab on the right. Here you will find the details of the successful / failed validations.

Parameterizing A Web Test This tutorial provides a brief introduction to the AppPerfect Web Test product using a set of handson practice exercises. This tutorial assumes you have successfully ed and installed AppPerfect Web Test on your machine with the default options. Apart from this pre-requisite, this tutorial is self contained. This document is divided into following sections 1. Creating Common Project 2. AppPerfect Web Test Within each section, multiple exercises are listed. Each exercise forms a logical unit which is expected to take no more than a few minutes to perform. All exercises use the PetStore demo application running inside Apache Tomcat. The modified PetStore application and Tomcat are both bundled with this product. All exercises assume you have installed the product in C:\AppPerfect\WebTest folder and will be referred as WebTest_HOME henceforth in tutorial. If you have installed the product in some other folder, modify the instructions below appropriately. This tutorial is not intended as a comprehensive training guide. Please refer to the product documentation for detailed information. However, this tutorial will give you a very good overview of the products and substantially improve your productivity with the product.

Creating Project Exercise 1: Launch AppPerfect Web Test 1. Click on Start -> Programs ->AppPerfect Web Test x.x.x -> AppPerfect Web Test 2. On launching AppPerfect Web Test a Welcome page will be displayed. Go through the brief description given for product. NB: Welcome page is displayed only when Web Test x.x.x is launched and last time no project was opened.

Exercise 2: Creating a Project 1. Launch the Define New Project dialog by clicking File ->New... menu option. The New Project wizard will be launched. 2. Keep the default project name and location for the purpose of this exercise. We don't have to provide "Notification" settings. Click on the OK button. 3. A confirmation message saying that the project is saved will be displayed. Click on the OK

button. Now using this project we will create tests to demonstrate the functionalities of AppPerfect Web Test product.


Exercise 1: Define a Web Test project 1. Once the project is successfully created another dialog - Define Project Properties dialog will be displayed. 2. The dialog shows various options which can be configured for the project, in "Where N=", specify 3 for three iterations since we shall be demonstrating the test using two parameters each having three parameters values using unique values for each test. Click on OK button. 3. Click through all the menu items to familiarize yourself with the available features and how to access them. Viewing through all menu items will give a reasonable overview of the application. 4. Click Help -> Table of Contents menu item to see AppPerfect Web Test product documentation 5. Open the Preferences dialog by selecting the menu option Tools -> Options... 6. Review the default settings for Web Test and click the OK button to close the dialog.

Exercise 2: Creating required parameters To demonstrate parameterization, we will consider the "" page of Petstore which has a page that takes a name and a . For this we will be defining three different parameters values each for and to be used while replaying the test. 1. Start tomcat server by selecting Start->Programs->AppPerfect WebTest x.x.x>Documentation and Examples->Examples->Tomcat running Petstore->Start Server. 2. Start web browser and enter the URL to load the petstore app. i.e. "http://localhost:8392/ petstore" 3. Click on link "enter the store". 4. Click on link "". 5. Here, Under "No. I would like to sign up for an .", create three s. For this tutorial we'll assume the following three s: ❍ 1: name - john, - smith. ❍ 2: name - sam, - bradley. ❍ 3: name - pet, - store.

We shall be leaving default information for " Information" on submitting the new name and . Sign-out and repeat process to add all the names and s. 6. Finally sign-out and close the browser.

Exercise 3: Recording a Test 1. To start recording, click on Project -> Record test... in the menu bar.' 2. 'AppPerfect Recorder' dialog will be displayed. Select the browser with which you need to record from the Browser drop down. Select ActionGroup1 from the Group combo. Provide starting URL as "http://localhost:8392/petstore". In the authentication select "HTML Form based " and provide name: "john" and :"smith". Now Click on 'Start recording' button. 3. An instance of selected browser will be launched with the PetStore home page loaded. Click on enter the store link. This will populate the database and display the PetStore main page. Note that populating the database might take some time. 4. 5. 6. 7. 8.

In IE click on link "Birds" to see list of products available in "Birds" category. Click on link "Amazon Parrot" to see details of this product. Click on "Add to Cart" to add Amazon Parrot. Check out by clicking on the Check Out link. Here, under "Are You a returning customer - Yes.", enter name as john and as smith. Click Submit. 9. Sign out of PetStore by clicking on Sign-out at top right of screen. 10. Close browser by clicking on File -> Close in the browser window. 11. 12. 13. 14.

Click on the Stop button of "AppPerfect Recorder" dialog to stop the recording session. Click on Close button to close the 'AppPerfect Recorder' dialog. Save project by selecting File->Save menu. In the AppPerfect Web Test window, look at the tree on the left. Each action you performed has been recorded. 15. Click on any of the recorded action on the left. The page associated with that action is displayed along with the actual element highlighted.

Exercise 4: Configuring Parameters in Test 1. In the editor tree, select 'Parameters' node to open the parameters settings table on the right hand side. 2. Here, click on 'Add Parameter' button to add a parameter. 3. In the 'Parameter Setting Dialog', enter 'Param' as the parameter name. 4. Select 'Fixed Values' as Data Source. 5. Choose 'Sequential' as parameter selection. 6. Under Add Value, enter john and click on the 'Add' button.

7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25.

26. 27. 28. 29. 30. 31.

Under Add Value, enter sam and click on the 'Add' button. Under Add Value, enter pet and click on the 'Add' button. Click Ok. Click on 'Add Parameter' button to add another parameter. In the 'Parameter Setting Dialog', enter 'Param' as the parameter name. Select 'Fixed Values' as Data Source. Choose 'Sequential' as parameter selection. Under Add Value, enter smith and click on the 'Add' button. Under Add Value, enter bradley and click on the 'Add' button. Under Add Value, enter shop(a wrong as per the we created for name pet, the correct was "store") and click on the 'Add' button. Click Ok. In the editor tree select the event which states something like 'set on WebInputElement Name1 : john'. In the details tab Click on the "text" argument in the Event Arguments table. Click on the 'parameterize' button. In the parameterization settings dialog, select "text" under the name column in the parameter settings table. On selection, in the value group, 'Constant' will be selected with the value john in the text box. Select 'Parameterize' and from the combo box, select Param. This will use the values of Param as name on each iteration. Click Ok. In the editor tree select the event which states something like 'set on WebElement : c21pdGg='. Its the second event below the event which states 'set on WebInputElement Name1 :john'. In the details tab Click on the "text" argument in the Event Arguments table. Click on the 'parameterize' button. In the parameterization settings dialog, select text under the name column in the parameter settings table. On selection, in the value group, 'Constant' will be selected with the value smith in the text box. Select 'Parameterize' and from the combo box, select Param. This will use the values of Param as the on each iteration. Click Ok.

Exercise 5: Executing a test - Watching the parameters in action. 1. To execute the test, click on Project -> Run from the menubar. 2. You can see the AppPerfect Web Test iterate through each recorded url/event and for the name and events, the parameter values will be substituted accordingly. 3. After 3 iterations Web Testing will stop and it will switch to Results view. In Result view you can analyze the final result.

4. Stop running tomcat server by selecting Start->Programs->AppPerfect Web Testx.x.x>Documentation and Examples->Examples->Tomcat running Petstore->Stop Server.

Validating A Web Test This tutorial provides a brief introduction to the AppPerfect Web Test product using a set of handson practice exercises. This tutorial assumes you have successfully ed and installed AppPerfect Web Test on your machine with the default options. Apart from this pre-requisite, this tutorial is self contained. This document is divided into following sections 1. Creating Project 2. AppPerfect Web Test Within each section, multiple exercises are listed. Each exercise forms a logical unit which is expected to take no more than a few minutes to perform. All exercises use the PetStore demo application running inside Apache Tomcat. The modified PetStore application and Tomcat are both bundled with this product. All exercises assume you have installed the product in C:\AppPerfect\WebTest folder and will be referred as WebTest_HOME henceforth in tutorial. If you have installed the product in some other folder, modify the instructions below appropriately. This tutorial is not intended as a comprehensive training guide. Please refer to the product documentation for detailed information. However, this tutorial will give you a very good overview of the products and substantially improve your productivity with the product.

Creating Project Exercise 1: Launch AppPerfect Web Test 1. Click on Start -> Programs ->AppPerfect Web Test x.x.x -> AppPerfect Web Test 2. On launching AppPerfect Web Test a Welcome page will be displayed. Go through the brief description given for product. NB: Welcome page is displayed only when Web Test x.x.x is launched and last time no project was opened.

Exercise 2: Creating a Project 1. Launch the Define new Project dialog by clicking File ->New... menu option. The New Project wizard will be launched. 2. Keep the default project name and location for the purpose of this exercise. We don't have to provide "Notification" settings. Click on the OK button. 3. A confirmation message saying that the project is saved will be displayed. Click on the OK

button. Now using this project we will create tests to demonstrate the functionalities of AppPerfect Web Test product.


Exercise 1: Define a Web Test project 1. Once the project is successfully created another dialog - Define Project Properties dialog will be displayed. 2. The dialog shows various options which can be configured for the project, in "Where N=", specify 2 for two iterations. Click on OK button. 3. Click through all the menu items to familiarize yourself with the available features and how to access them. Viewing through all menu items will give a reasonable overview of the application. 4. Click Help -> Table of Contents menu item to see AppPerfect Web Test product documentation 5. Open the Preferences dialog by selecting the menu option Tools -> Options... 6. Review the default settings for Web Test and click the OK button to close the dialog.

Exercise 2: Recording a Test 1. Start tomcat server by selecting Start->Programs->AppPerfect WebTest x.x.x>Documentation and Examples->Examples->Tomcat running Petstore->Start Server. 2. To start recording, click on Project -> Record test... in the menu bar.' 3. 'AppPerfect Recorder' dialog will be displayed. Select the browser with which you need to record from the Browser drop down. Select ActionGroup1 from the Group combo. Provide starting URL as "http://localhost:8392/petstore". In the authentication drop down select "HTML Form based " and provide name: "j2ee" and :"j2ee". Now Click on 'Start recording' button. 4. An instance of selected browser will be launched with the PetStore home page loaded. Click on enter the store link. This will populate the database and display the PetStore main page. Note that populating the database might take some time. 5. 6. 7. 8. 9.

Click on link "Birds" to see list of products available in "Birds" category. Click on link "Amazon Parrot" to see details of this product. Click on "Add to Cart" to add Amazon Parrot. Check out by clicking on the Check Out link. Here, under "Are You a returning customer - Yes.", enter name as j2ee and as j2ee. Click Submit.

10. Sign out of PetStore by clicking on Sign-out at top right of screen. 11. Close browser by clicking on File -> Close in the browser window. 12. 13. 14. 15.

Click on the Stop button of "AppPerfect Recorder" dialog to stop the recording session. Click on Close button to close the 'AppPerfect Recorder' dialog. Save project by selecting File->Save menu. In the AppPerfect Web Test window, look at the tree on the left. Each action you performed has been recorded. 16. Click on any of the recorded action on the left. The page associated with that action is displayed along with the actual element highlighted.

Exercise 3: Configuring Parameters in Test 1. In the editor tree, select 'Parameters' node to open the parameters settings table on the right hand side. 2. Here, click on 'Add Parameter' button to add a parameter. 3. In the 'Parameter Setting Dialog', enter 'Param' as the parameter name. 4. Select 'Fixed Values' as Data Source. 5. Choose 'Sequential' as parameter selection. 6. Under Add Value, enter j2ee and click on the 'Add' button. 7. Under Add Value, enter john and click on the 'Add' button. 8. Click Ok. 9. In the editor tree select the event which states something like 'set on WebInputElement Name1 : j2ee'.. 10. In the details tab click on the "text" argument in the Event Arguments table. 11. Click on the 'parameterize' button. 12. In the parameterization settings dialog, select "text" under the name column in the parameter settings table. 13. On selection, in the value group, 'Constant' will be selected with the value j2ee in the text box. 14. Select 'Parameterize' and from the combo box, select Param. This will use the values of Param as name on each iteration. 15. Click Ok.

Exercise 4: Configuring Text Validation 1. In the editor tree select the task which states something like 'Welcome to the BluePrints Petstore'. 2. In the DOM tree on the right hand side, right click and select 'Add Text Validation' in the popup menu. 3. This will bring up the 'Text Validation Settings' dialog. 4. Under description enter 'NameText'. 5. Under 'Check for', select 'Exact match' and enter j2ee.

6. Click Ok. What this basically does is that when this page loads (on replaying), it will search the page for the text j2ee and if it is not found, the validation will fail. Since we have parameterized the name, on the 2nd iteration, the name ed will be john which does not exist. As a result of which, this page will not replayed as expected and the validation will fail.

Exercise 5: Configuring Element Attribute Validation 1. In the editor tree select the task which states something like 'Sign-on' 2. Expand the right-hand side tree and select the element 'Name1' which will highlight the 'Name' text box under 'Are you a returning customer - Yes'. 3. Right-click on this element and select 'Add Validation'. 4. This will bring up the 'Add Vaidation' dialog. Check 'Validate' for the row whose property name is 'value' and property value is 'j2ee'. 5. Click Ok. 6. Select the 'Validation' tab below. In the validation table, select the validation just added and click 'Parameterize..' button. 7. This will bring up the 'Parameterization Settings Dialog'. Here change the constant value from j2ee to john. 8. Click Ok. 9. What this basically does is that when this page loads (on replaying), it will confirm the value in the text box with john. Since in both our iterations, the initial value (when the page loads) will be j2ee, the validation will fail in both iterations.

Exercise 6: Executing a test 1. To execute the test, click on Project -> Run from the menubar. 2. You can see the AppPerfect Web Test iterate through each recorded url/event and for the name and events, the parameter values will be substituted accordingly. 3. After 2 iterations Web Testing will stop and it will switch to Results view. In Result view you can analyze the final result. 4. Stop running tomcat server by selecting Start->Programs->AppPerfect Web Testx.x.x>Documentation and Examples->Examples->Tomcat running Petstore->Stop Server.

Introduction The Internet has become the de facto standard means by which most people interact with a vast majority of software application. This move away from desktop computing to server-side computing with HTML as the front-end technology has created a whole new class of applications to be built and delivered to customers. However, it has also created a new set of challenges in of developing and testing these applications. It is now assumed your customer may be sitting thousands of miles away and working in a language you are not familiar with. A second aspect of modern software development methodology is to start testing the software early and often. Most software developers do not follow the cascading model of development whereby testing only starts after development ends. Further, developers are being increasingly encouraged to create vast arrays of unit tests to ensure quality.

Need for Web Test All software is designed and developed to meet and satisfy certain "functional" needs. A functional need may be technical, business, or process. A key component of testing a software is to ensure that it functionally does what it is supposed to do. Functional Testing is the process by which expected behavior of an application is tested. Most software undergo changes over a period of time. These changes may occur during initial development of the software, or after the release of the software. Any change to the software carries a potential of errors or bugs being introduced. Regression Testing is the process of frequently retesting a software to ensure known existing behavior or functionality is not impacted. By impacted, we mean either modified or broken. If behavior is modified, the developer or tester must ensure that it is expected. Otherwise, it is called a "Regression". As the size and complexity of applications have grown over the years, it has become increasingly difficult to ensure functional compliance and to ensure no regressions over time. Even a small size project can generate excessive permutations and combinations of test cases that are too great for a human to test consistently and continually. Hence, it is critical to find a testing system which can be automated. The AppPerfect Web Test was created to assist s with such challenges. Since the mechanics of Functional Testing and Regression Testing are similar, they can be addressed with a single testing tool. AppPerfect Web Test provides for "recording" a test once and then "replaying" it when desired without additional manual intervention in an automated manner.

AppPerfect Web Test Key Features

AppPerfect Web Test is a comprehensive Web application testing solution that provides all the features you need, to ensure the reliability of your business-critical applications. ●

●

●

●

●

●

●

●

●

●

●

Technologies : AppPerfect Web Test s testing applications based on .NET, ASP, Servlets/JSP, CGI, SSL and most other server-side Web technologies. It also s advanced Web technologies such as AJAX, Flash and Java Applets. Browser recording: You can use the browser recording facility to create the tests as you would normally work with your application. There is no need to learn any proprietary scripting language. You can then edit and run the test fast and easily. Recording s JavaScript dialogs, File Chooser dialogs, Menus, toolbar etc apart from normal HTML elements. Recording is Component-based and not co-ordinate based allowing to replay test even when browser is moved or element position changes. Web Test s recording from multiple instances of browser simultaneously. Multiple Browsers ed: Recording/Replaying is ed on most commonly used browsers like Internet Explorer, Mozilla Firefox and Safari. UI based editing of tests: The UI is easy to use and allows you to edit your existing test as well as add new URLs and parameters to the test. You can quickly modify your tests and easily build on the Test Cases as and when additional functionality is added to your products Reduced testing time: As the tests for AppPerfect Web Test are fully automated, you can save a substantial amount of time and resources that would be spent on trying to test the system manually. Also errors that might be overlooked during manual testing are caught by the AppPerfect Web Test and there is no bias in the reporting of errors. AppPerfect Web Test helps you improve the quality of your Web Applications and drastically reduces the time it would take to get your product out into the market. Scripting : For advanced AppPerfect Web Test provides scripting language . The scripting language used is simple java script, s can view/edit the test using script editor provided. s can customize a test as much as they want using java script. Parameterize Tests: In real world scenario, for any Web-based application, the pages that are requested are not all static. In fact, most of the pages accept some parameters as input and then correspondingly show the appropriate customized content. Parameterize tests feed these parameters automatically to the request and thus help simulate a more realistic usage environment. AppPerfect can read values from text files, databases etc. Response Validation: You can validate the responses received for a URL request with AppPerfect Web Test. You can customize what constitutes a valid or invalid response for an URL request. for basic authentication, cookies, SSL: With the AppPerfect Web Test, you can test URLs that require basic authentication as well as those using HTTPS by allowing the configuration of the SSL Provider. It also handles the sending of cookies with the appropriate requests and s URL rewriting if your application uses it. Two way SSL authentication is also ed. Execution without launching browser: AppPerfect Web Test provides for running tests without launching browser. Events on all HTML elements is ed in this mode. Limitation of this mode is that it cannot run window events like events on Applets, Flash, javascript dialogs, Toolbar buttons, Menu bar etc. Remote Execution of tests with Central Controller: AppPerfect Web Test provides for creation of test on one machine and execution of same remotely on multiple

●

●

●

●

●

●

●

●

machines simultaneously. This way you can run functional test from multiple machines and can control the functional test from one central machine. At the end of execution application will present the functional testing result of entire functional test as well as individual machines. This requires AppPerfect Web Test to be installed on remote machines. Object Spy: AppPerfect Web Test provides functionality to Spy on any HTML element in the page and fetch its properties. This makes it easier to add any new HTML element to your existing functional test and build on the Test Cases as and when additional functionality is added to your product Importing of tests / groups: AppPerfect Web Test can import a test that has been created using the AppPerfect Load Test. This makes it easy for a to create a test instead of replicating the effort of creating a test. One can also import already recorded groups from one test to another. Informative reports: The application provides reports that help you pin point failure points of the test. These reports are available through the UI and can be exported into different formats: HTML, PDF, CSV, XLS and XML. Trend Analysis: AppPerfect Test Manager provides lot of trend reports for trend analysis of your application. This utility takes multiple result files and generates trend charts and reports based on the data found. You need AppPerfect Test Manager for trend analysis Scheduling of tests: You can schedule your tests with AppPerfect Test Manager. You do not have to be physically present to start the test. The whole process is automated so you can schedule a test to run in the night and have a look at the results the next day and then correct any errors found by the test. You need AppPerfect Test Manager for scheduling tests. Notification of results: You can configure AppPerfect project to notify results using Email or custom notification mechanism. In case of Email notification you can specify whether you want results as attachment and AppPerfect will export the results as HTML file and send the same as attachment with the mail. IDE Integration: AppPerfect Web Test s IDE integration with most commonly used IDEs. This enhances ease-of-use and productivity. Currently ed IDEs are Eclipse, NetBeans, IntelliJ, JBuilder, JDeveloper, BEA Workshop, IBM RAD, IBM Websphere Studio etc,. ANT Integration and Command line execution: AppPerfect Web Test s ANT Integration and command line execution so you can functional test your web application by invoking product by running ANT script or by running bat/sh file.

About AppPerfect Products AppPerfect offers following products for complete and comprehensive solution for testing and monitoring the performance of your application. These products that are designed to help you test your application throughout the development life-cycle.

AppPerfect Java Unit Test: AppPerfect Java Unit Test is a feature-rich wrapper for the popular JUnit and HtmlUnit testing frameworks for non-web and web-based Java projects respectively. It provides the Java programmer with an easy to use and fully customizable unit-testing environment, which can be

integrated with popular Java IDEs as well as the project's build process.

AppPerfect Java Code Test: AppPerfect Java Code Test reads your software code and analyzes it for optimization, errors, coding conventions, complexity and style based on industry-standard rules. Over 750 pre-defined, high-value rules can be applied to your code. AppPerfect Java Code Test is an ideal tool to perform code reviews on an on-going basis to ensure high quality of code.

AppPerfect Java Profiler: AppPerfect Java Profiler profiles a Java Virtual Machine to assist you in understanding the behavior of your application as it performs its functions. AppPerfect Java Profiler recognizes that your application does not operate in a vacuum and hence provides a unique blend of Java information combined with operating system information.

AppPerfect App Test: AppPerfect App Test performs regression and functional testing of your Windows/Desktop applications. Performing manual functional testing by having a person sit and manually click away at the application is extremely expensive and error-prone. AppPerfect App Test provides the means to perform such labor-intensive activity in an automated manner.

AppPerfect Web Test: AppPerfect Web Test performs regression and functional testing of your Web applications. Performing manual functional testing by having a person sit and manually click away at the application is extremely expensive and error-prone. AppPerfect Web Test provides the means to perform such labor-intensive activity in an automated manner.

AppPerfect Load Test: AppPerfect Load Test is a stress/load testing tool that can simulate hundreds of virtual s from a single machine. Features ed include site recording, dynamic variable substitution, cookies , session tracking, SSL and run strategies. It can run tests based on a variety of strategies such as burst, incremental, exponential, quadratic or loop. It also provides you a comprehensive solution to monitor various attributes of various operating systems present in your application infrastructure.

AppPerfect Test Manager: The AppPerfect Test Manager is central server with a Web-based UI for accessing various modules in the server. AppPerfect Test Manager consists of five main modules:

Requirements Manager: This module is used to create requirement specifications around which your tests will be designed and executed. Functional, business, performance, technical and usability requirements should be defined here to ensure the tests cover all defined criteria. Test Manager: Once tests have been designed, the Test Manager can be used to manage the execution of your tests. Automatically running tests on a specific schedule, notification of test results, saving of test results, etc. can be defined in this module. Results Manager: Once results for your various tests have run a few iterations, the Results Manager can be used to manage the archived results. Trend Analysis of multiple results to detect key quality trends is a key feature of this module. Storage management can also be performed via this module. Issues Manager: As tests are run, issues such as defects, enhancements, modifications, etc. will occur. This module can be used to create and track such issues. This module is designed as a lightweight issues manager that seamlessly integrates with the rest of the server and is not intended to replace full-featured issues management system. License Manager: Floating/site licenses are managed using this module. This module acts as the central manager for issuing and reclaiming floating licenses for the AppPerfect products.

AppPerfect Agentless Monitor: The AppPerfect Agentless Monitor is an agentless, Web-based monitoring solution. It helps you monitor your applications and the underlying system resources. The AppPerfect Agentless Monitor consists of: AppPerfect Monitor: A pure Web-based solution that helps you monitor your application infrastructure. Provides a rules engine to define alerts: a notification server for email and SMS notifications. Also includes a powerful report designer to create custom reports to analyze and understand the performance data. AppPerfect Monitors: A series of modules designed to specific devices. AppPerfect Monitor does not use the traditional agents-based approach to monitoring. Apart from being expensive, agents-based approach is also highly complex and error-prone. AppPerfect Monitors are designed to impose negligible overhead on the monitored system. These monitors are superbly optimized programs providing the maximum amount of information while imposing the lowest possible overhead. Currently, the following devices are ed: ● ● ● ●

Java/J2EE App Servers (Tomcat, WebLogic, WebSphere, etc.) Operating Systems Resources (Windows, Linux, Mac OS X) Databases (Oracle, MySQL, MS SQL, DB2, Sybase) Web Servers (Apache HTTP Server, MS IIS)

● ● ●

SNMP Monitors (v1 and v2) Ping Monitor (Device heartbeat monitor) Mail Server (MS Exchange)

About AppPerfect Corporation AppPerfect Corporation is an independent software development company dedicated to providing the developer community with the best-in-class tools throughout the entire software life-cycle. Our aim is to be your primary vendor for most of your development- and deployment-tool needs. Our mission is to help you reduce your software development costs, increase your productivity and help improve the availability and scalability of your applications. Please visit us on the Web at www. AppPerfect.com for more information.

Building a Web Project The steps to create a Web project are as under: ●

Project

●

Project Function

Project If you are creating a Web Test project from scratch without visiting Web Test perspective for a project then you need to do the following: 1. an entry for Web Test in the project file (*.awt). Open the project file present in the project location with an extension AWT and name same as project name e.g. NewProject. awt. Add an entry above the tag if such an entry is absent. 2. Creating a new script file with the name same as project and appending "_ft.js" to it. for e.g. NewProject_ft.js 3. Defining global function calls and declaring project_function. Open the script file in an editor and add following entries to the file and save it: importPackage(Packages.com.appperfect.devcommon.script); importPackage(Packages.com.appperfect.functionaltester.script); var engine; //Variable to store instance of ScriptEngine Instance function project_function() // script function for Web Test project NewProject { var webtest = engine.createWebTest(); } This will create a default Web Test project. We will learn more about project_function in the next section.

function project_function( ) This function configures the Functional Test as a whole. It configures the run settings, no of group along with group settings. It also defines test parameters. First task is to create the project using following statement: var webtest = engine.createWebTest(); There is a restriction that the name of the project variable should be webtest. The script file is parsed to keep script & UI in synchronization. Once the Functional test is created we will configure it by calling various APIs on it. ●

Think time is a duration in seconds which denotes the amount of wait time between each

●

●

task while replaying. Depending upon processing of the request at the server end it can be a significant value which if ignored may result in task timed out during replaying. AppPerfect Web Test allows you to record the think time during recording and then either ignore or use it during replaying. It also allows to set default think time for tasks which do not have any significant think time. Following APIs can be used to configure think time for the tasks in the test. ❍ void setDefaultThinkTime(int seconds); ❍ void setRecordThinkTime(boolean record); ❍ void setIgnoreThinkTimeWhileReplaying(boolean ignore); Time Out : To mark a task as timed out if it was unable to fetch a response or was unable to find the desired element after specified duration we need to set time out duration. This can be done by using void setTimeOut(int seconds); API. Cache settings : After one iteration of the test run, it is quite possible that some of the response may be cached for e.g. image files etc. This will affect next iteration and may not give real life simulation of task execution. The cache can be cleared before each iteration or before start of replaying by calling following APIs. void clearBrowserPrivateData(int when); where 'when' should be one of the following values: ■ IWebTest.CLEAR_AT_START_OF_TEST for clearing at start of replaying ■ IWebTest.CLEAR_AT_START_OF_EVERY_ITERATION for clearing at start of each iteration ❍ void clearBrowserCache(boolean clear); ❍ void clearBrowserHistory(boolean clear); ❍ void clearCookies(boolean clear); Save Successful responses : By default only failed task responses and images are saved, In case you need to also save successful responses use void setSaveSuccessfulResponseDetails(boolean save); API. ❍

●

●

●

Iteration settings : By default test replays for single iteration. To set number of iterations for test use void setNoOfIterations(int iterations); API. In case you need to run test for all the possible paramter combination then use void setIterateTestForAllParameterCombinations (boolean all); API. Replaying in Non-UI mode : To replay test without launching browser, use void setReplayTestInNonUIMode(boolean replayInNonUI); API.

Configuring Database The steps to configure and a Database Connection with Web Test are as under: ●

Defining database ID

●

Other database operations

Defining database ID For any interaction with a database of your interest it is very necessary to the database along with its properties with AppPerfect Web Test. While ing the database, a unique database Id needs to be ed as first parameter and any further database interaction through Web Test should be performed by ing this unique database id. Database can be ed by calling String setDatabaseConnection( String uniqueDatabaseId, String connectionURL, String Name, String , String driverClass, String classPath); API. For e.g. var database = engine.setDatabaseConnection('Northwind', 'jdbc:oracle:thin:@localhost:1543: Northwind', 'scott','tiger', 'oracle.jdbc.driver.OracleDriver', 'C:\DatabaseDrivers\ojdbc14.jar'); This will an Oracle database "Northwind" with database id Northwind and it will return the database vendor i.e. It will return "Oracle" If the vendor is not a well-know database vendor it will return "Other"

Other database operations Once a database ID is defined, database operations can be performed during execution of the test for various purpose like validating if a s table contains an entry of a after a task of adding was performed. AppPerfect Web Test provides following APIs to perform database operations: 1. boolean isDatabaseConnectionValid(String uniqueDatabaseId); to check if database connection is valid 2. Object getValueFromDatabase(String uniqueDatabaseId, String query, int row, int column); to fetch a value present at row,column after executing a select query. for e.g. var value = engine.getValeuFromDatabase('Northwind', 'Select CategoryName from Categories', 2, 1); to get the value present in 2nd row 1st column of the ResultSet after executing 'Select CategoryName from Categories' query. 3. int getNumberOfDatabaseRows(String uniqueDatabaseId, String query); returns no of rows present in the result set after executing the specified query 4. int getNumberOfDatabaseColumns(String uniqueDatabaseId, String query); returns the no of columns present in the result set after executing the specified query 5. ResultSet getResultSet(String uniqueDatabaseId, String query); returns java.util.ResultSet whose APIs can be used to iterate through the complete ResultSet after executing the query

6. ResultSet executeSelectQuery(String uniqueDatabaseId, String query); returns java.util. ResultSet whose APIs can be used to iterate through the complete ResultSet after executing the query 7. boolean closeResultSet(ResultSet resultSet); to close the ResultSet which was created using above APIs. 8. int executeInsertUpdateQuery(String uniqueDatabaseId, String query); returns count of rows affected by Update, Insert or delete query. This API should be used carefully as changes the state of database. 9. String getLastError(); to get the last error occured during any database operation or SQL transaction

Test Parameters Project Parameter are used in most modern applications to communicate data between the and the application. AppPerfect offers extensive parameter-management. Parameter selection and hence testing with various parameter values is completely automated. Parameter values are ed either via the URL itself or via the HTTP header object. In the AppPerfect application, parameters are stored as name-value pairs, making it intuitive for application developers and testers. Then, depending on the number of iterations for your project, multiple parameter values can be tested, with options to select parameters sequentially or randomly. ●

Adding test parameter

●

Setting values of a parameter

●

Fetching values from SQL database

●

Fetching values from CSV file

●

Fetching values by performing mathematical operations

●

through test parameters

Adding test parameter To add a test parameter to the project, you have to use void addTestParameter( String name, boolean randomSelection, boolean sameParameterValues); API. The name of the parameter should be unique. i.e. there cannot be 2 test parameters with the same name. You can specify is the application should select the values sequentially or randomly and you can also specify if application should choose unique values always i.e. no to repeat the values till all of them have been used. For e.g. webtest.addTestParameter('bird_name', false, true); adds a test parameter with the name bird_name to the project. This parameter then can be used in different tasks which will pick the values from it.

Setting values of a parameter Once the test parameter is added to the project, and if you are aware of the set of values it should pick up the values from, you should use void setParameterValues(String parameterName, String [] values); API to set the set of values. For e.g. var values = ['Parrot', 'Crow', 'Piegon', 'Finch']; webtest.setParameterValues('bird_name', values);

Fetching values from SQL database

Quite often the set of values that a parameter can take is not know before hand and its value is available at runtime by querying a database. This can be achieved by setting the source of the test parameter as a database instead of specifying the values. You need to define a database ID prior to using this method which has been explained in previous chapter Defining database ID. Once the database ID is defined, you can use void setDatabaseDatasource( String parameterName, String databaseId, int whenToFetch, int noOfRows, String query); API to fetch the values from the database. The query should be a select query having only 1 column, If the ResultSet contains more than 1 column values from 1st column will be taken ignoring other columns. You can also specify when the application should fetch the values from the database by ing appropriate constant as the 3rd parameter. Possible values are: ● ●

●

●

●

IScriptTest.FETCH_VALUES_NOW to fetch values now IScriptTest.FETCH_VALUES_RUNTIME_BEFORE_TEST_EXECUTION to fetch values before the execution begins IScriptTest.FETCH_VALUES_RUNTIME_BEFORE_TASK_OR_EVENT_EXECUTION to fetch values before the execution of the task or event in which it is used IScriptTest.FETCH_VALUES_RUNTIME_AFTER_TASK_OR_EVENT_EXECUTION to fetch values after the execution of the task or event in which it is used IScriptTest.FETCH_VALUES_EVERYTIME to fetch values everytime this test parameter is used

For e.g. webtest.setDatabaseDatasource('bird_name', 'Northwind', IScriptTest. FETCH_VALUES_RUNTIME_BEFORE_TEST_EXECUTION, 10, 'Select bird_name from birds');

Fetching values from CSV file Quite often the set of values that a parameter can take is not know before hand and its value is available at runtime by reading a CSV file. This can be achieved by setting the source of the test parameter as a CSV file instead of specifying the values. You can use void setCSVDatasource (String parameterName, String fileName, int columnIndex, int whenToFetch, boolean firstRowHeader, int noOfRows, String valueDelimiter, String stringDelimiter); API to fetch the values from the CSV fiile. You can also specify when the application should fetch the values from the database by ing appropriate constant as the 4th parameter. Possible values are: ● ●

●

●

●

IScriptTest.FETCH_VALUES_NOW to fetch values now IScriptTest.FETCH_VALUES_RUNTIME_BEFORE_TEST_EXECUTION to fetch values before the execution begins IScriptTest.FETCH_VALUES_RUNTIME_BEFORE_TASK_OR_EVENT_EXECUTION to fetch values before the execution of the task or event in which it is used IScriptTest.FETCH_VALUES_RUNTIME_AFTER_TASK_OR_EVENT_EXECUTION to fetch values after the execution of the task or event in which it is used IScriptTest.FETCH_VALUES_EVERYTIME to fetch values everytime this test parameter is used

For e.g. webtest.setCSVDatasource('bird_name', 'C:\birds.csv', 1, IScriptTest.

FETCH_VALUES_RUNTIME_BEFORE_TEST_EXECUTION, true, 10, ',', '"');

Fetching values by performing mathematical operations AppPerfect Web Test also provides an advanced data source where is values are not fetched from a persistence resource like database OR CSV file but are calculated using a defined formulae. This type of a datasource can be specified in two different ways viz; void setNumberCalculationDatasource (String parameterName, String prefix, String suffix, boolean autoNumber, int start, int end, boolean increment, int incrementBy, int resetCriteria, int lastValue); for numeric values and void setDateCalculationDatasource(String parameterName, String format, boolean todaysDate, String start, String end); for date related values. For e.g. webtest.setNumberCalculationDatasource('bird_name', 'Parrot', '', false, 1, 10, true, 1, 1, 1); webtest.setDateCalculationDatasource('bird_purchase_date', 'MM-dd-yyyy', '01-01-2000', '12-312004');

through test parameters Another category of parameters ed by AppPerfect Web Test is that of "through". These parameters are such that its values are set by server and are sent to the client. For e.g. SessionID, hidden parameters in the form. By defining this type of a parameter, AppPerfect Web Test will search in the previous response value of the parameter and use it for subsequent requests. This can be achieved by calling void setthroughDatasource(String parameterName, boolean searchInScript, boolean searchInHTML); API. You can also configure if the value of the parameter should be searched in javascript functions and/or in pure HTML elements. For e.g. webtest.setthroughDatasource('bird_type', false, true);

Task groups in Web Project A task group is a collection of task in a project. A task group can either contain browser element, url (HTTP/HTTPS) tasks, web HTML elements or window elements. ●

Adding task group

●

Setting group properties

Adding task group An Action group can be added to the test using IWebGroup addActionGroup(String groupName, String startingURL, int repeatCount, boolean ignore); API. It returns a web group. Ignore paramter should be set to true if you want to ignore the group during execution. Multiple action groups can be added to test by calling the same API again with different parameters. For e.g. var group = webtest.addActionGroup('ActionGroup1', 'http://localhost:8081/petstore', 1, false); adds a web group with name ActionGroup1 and starting URL http://localhost:8081/petstore. In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'group'.

Setting group properties Once a group is created you need to set various properties of the group in order to execute tasks in this group. Quite often the web applications being tested are not simple applications and require different types of authentications during the execution of the test. AppPerfect Web Test provides various APIs to set authentication credentials. By default a group doesn't require any authentication credentials. AppPerfect Web Test Form, Basic, Digest, NTLM types of authentication. To set the type of authentication use void setAuthenticationMechanism(int mechanism); API. Possible values for mechanism are: ● ● ● ● ●

IWebGroup.NO_AUTHENTICATION IWebGroup.FORM_AUTHENTICATION IWebGroup.BASIC_AUTHENTICATION IWebGroup.DIGEST_AUTHENTICATION IWebGroup.NTLM_AUTHENTICATION

name for any type of authentication should be set by calling void setAuthenticationName (String name, boolean parameterised); API. If name is parameterised then the second value to be ed in true and the first parameter is the name of the test parameter. If the name is not parameterised then actual name is ed as the first parameter.

for any type of authentication should be set by calling void setAuthentication (String , boolean parameterised); API. If is parameterised then the second value to be ed in true and the first parameter is the name of the test parameter. If the is not parameterised then actual is ed as the first parameter. void setAuthenticationDomainName(String domain); API is called to set the Domain name if the authentication is of type IWebGroup.DIGEST_AUTHENTICATION. Finally if the web or application server is configured for authenticating the client based on client certificates, you need to client certificates witht eh group by calling following APIs: ●

●

void setUseClientSSLAuthentication(boolean flag); to set that group should use client SSL authentication void addClientCertificate(String , String certFilePath); to a client certificate for a group

Configuring tasks in a Web task group A task group is a collection of tasks. A task group can either contain browser task, url task, web/ HTML element or Window element task. We will discuss how to create a task in a task group and also about configuring and setting task properties in this chapter. Please read Task groups in Web Project chapter for further details on task groups. This chapter will cover all the tasks ed in Web Test: ●

Browser task

●

URL task

●

Web/HTML element task

●

Window element task

Browser task A browser task is equivalent to a web browser session. Following operations are possible for a Browser instance. ●

Creation of a Browser task

●

Configuring properties for a Browser task

●

Execution of a Browser task

●

Release of a Browser task

Creation of a Browser task Browser task can be created using createBrowser API of IScriptEngine interface. The return value is an instance of IBrowser interface. ●

IBrowser createBrowser(int id, String sTitle, String sURL); where, 'id' is the Task Id. It should be unique across the test. ❍ 'sTitle' is the unique title of the browser which is used to identify browser. ❍ 'sURL' is url with which the Browser should be opened ex. http://localhost:8080/ petstore For ex. var browser = engine.createBrowser(1, 'Browser_1', 'http://localhost:8080/petstore'); will create a browser instance with task id 1, title Browser_1 and starting URL http:// localhost:8080/petstore ❍

In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'browser'

Configuring properties for a Browser task Once a task is created, all its properties like think time, title, timeout period etc. can be initialised to proper values using appropriate apis exposed by individual tasks. Following APIs are ed by IBrowser interface for configuring properties of a Browser task. ●

void setThinkTime(int iThinkTime); where, 'iThinkTime' is wait time in no. of seconds for which the engine should wait before the task is actually executed. For ex. browser.setThinkTime(10); will set think time to 10 seconds. ❍

Execution of a Browser task Once a task is initialised it should be executed to fetch and process the results. Script engine takes the responsibility to execute a Browser task. It can be done using following API of IScriptEngine interface. ●

boolean executeBrowser(IBrowser browser); where, ❍

'browser' is IBrowser task instance, which we got from Creation of a Browser task

returns true if task was executed successfully, returns false if there is any failure during execution For ex. var successful = engine.executeBrowser(browser); will execute a Browser task. ❍

Release of a Browser task Once a task is executed it is must to call release method to release all the opened resources. It takes care to release all the internal objects like ResultSet, Connection etc. if any. Also this method takes care of saving the response/images if any to disk. This method should be always called in the end after the execution of each task. It can be done using following API of IScriptEngine interface ●

void release(); For ex. engine.release(); will release a Browser task.

URL task A URL task represents reponse for any HTTP/HTTPS request. It basically represents the response page shown in the web browser as a result of firing any request. Following operations are possible for a URL instance. ●

Creation of a URL task

●

Configuring properties for a URL task

●

Execution of a URL task

●

Release of a URL task

Creation of a URL task URL task can be created using createURL API of IScriptEngine interface. The return value is an instance of IUrl interface. ●

IUrl createURL(int id, String sURL, boolean bSubFrame); where, 'id' is the Task Id. It should be unique across the test. ❍ 'sURL' is url of the task ex. http://localhost:8080/petstore. ❍ 'bSubFrame' whether its a sub frame or top level page. Possible values are true for subframe and false for top level page For ex. var url = engine.createURL(2, 'http://localhost:8080/petstore', false); will create a top level url instance with task id 2, and URL http://localhost:8080/petstore ❍

In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'url'

Configuring properties for a URL task Once a task is created, all its properties like think time, title, timeout period etc. can be initialised to proper values using appropriate apis exposed by individual tasks. Following APIs are ed by IUrl interface for configuring properties of a URL task. ●

void setTimeOut(int iTimeOut); where,

●

'iTimeOut' in no of seconds for the task to complete its execution. Few urls may take long time to respond, sometimes forever, due to various reason like server is not responding, network failure etc. This could affect the test execution which will never complete. One can come out of this situation by specifying the no of seconds after which the task execution will be aborted and its status will be marked as timed out. For ex. url.setTimeOut(20); will set time out period to 20 seconds. void setIgnored(boolean bIgnore); where, ❍

'bIgnore' whether task should be ignored during execution. Possible values are true if task should be ignored, false otherwise. For ex. url.setIgnored(false); will ignore execution of task. ❍

●

void setBenchmarkFile(String sFileName); This is helpful for validation purpose to match the replayed response with the recorded one. where, 'sFileName' is relative file path of the response when this task was recorded. Path is relative to the project location. For ex. url.setBenchmarkFile('recorded/2006_12_1_13_39_1_50/ActionGroup1/URL_2. html'); void setTitle(String sTitle); where, ❍

●

❍

'sTitle' title of the page

●

For ex. url.setTitle('AppPerfect'); void setIgnoreParam(boolean bIgnore); This API is used to decide if URL parameters comparision should be ignored during execution. where, 'bIgnore' is true if the parameters comparision should be ignored; false otherwise For ex. url.setIgnoreParam(true); will ignore URL parameters comparision during execution. ❍

●

void setBreakPoint(boolean bBreakPoint); In case breakpoint is set, test will wait for 's interruption before moving forward. where, ❍

●

'bBreakPoint' is true if breakpoint should be set; false otherwise.

For ex. url.setBreakPoint(false); will clear breakpoint. void setFireURL(boolean bFireURL); This method should be called in case url is to be fired explicitly. where, 'bFireURL' is true if url should be fired explicitly; false otherwise. For ex. url.setFireURL(false); will not fire url explicitly. void addParameter(String name, String value); A URL can have many request parameters. Each GET parameter needs to be added using this method. A parameter added using this method is appended to the URL when the URL is fired explicitly. where, ❍

●

'name' is name of the request parameter ❍ 'value' is value of the request parameter For ex. url.addParameter('name', 'AppPerfect'); ❍

If parameter is parameterised then the value for same should be fetched using following API of IScriptEngine ●

String getParameterValue(String name, String value, String parameterName, boolean beforeExecution); where, ❍ ❍ ❍ ❍

'name' is name of the parameter 'value' is recorded value of the parameter 'parameterName' is name of the test parameter 'bBeforeExecution' to indicate whether the test parameter should be populated before the execution of the task

returns resultant value of parameterisation For ex. var arg0 = engine.getParameterValue('name', 'AppPerfect', 'testparam1', true); ❍

Execution of a URL task Once a task is initialised it should be executed to fetch and process the results. Script engine takes the responsibility to execute a URL task. It can be done using following API of IScriptEngine interface. ●

boolean executeURL(IUrl url); where, ❍

'url' is IUrl task instance, which we got from Creation of a URL task

❍

returns true if task was executed successfully, returns false if there is any failure

during execution For ex. var successful = engine.executeURL(url); will execute a URL task.

Release of a URL task Once a task is executed it is must to call release method to release all the opened resources. It takes care to release all the internal objects like ResultSet, Connection etc. if any. Also this method takes care of saving the response/images if any to disk. This method should be always called in the end after the execution of each task. It can be done using following API of IScriptEngine interface ●

void release(); For ex. engine.release(); will release URL task.

Web/HTML element task A Web/HTML element represents any HTML element in the DOM. For furthur details on ed elements and APIs go though the points mentioned below : ●

Types of Web Element

●

Configuring properties for a Web element Task

●

Execution of a Web element task

●

Release of a Web element task

Types of Web Element Following types of web elements are ed in Web Test. Out of them, WebObject is generic element and can be used to represent any element not in the list. Please go through following elements for futhur details related to creation of each type of element and events ed on them. ●

WebObject

●

WebArea

●

WebButton

●

WebCheckBox

●

WebComboBox

●

WebDivElement

●

WebEdit

●

WebFile

●

WebHiddenField

●

WebImage

●

WebInputElement

●

WebInputButton

●

WebInputImage

●

WebLink

●

WebList

●

WebListItem

●

WebField

●

WebRadioButton

●

WebResetButton

●

WebSpan

●

WebSubmitButton

●

WebTable

●

WebTextArea

●

WebTextField

●

WebBrowserElement

In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

WebObject A WebObject represents a generic HTML element. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebObject : ●

Creation of a WebObject

●

ed events for a WebObject

Creation of a WebObject WebObject element can be created using createWebObject API of IScriptEngine interface. The return value is an instance of WebObject interface. ●

WebObject createWebObject(int id, String sElementTag, int iElementType); where, ❍ ❍ ❍

'id' is the Task Id. It should be unique across the test. 'sElementTag' is the HTML tag name used to identify element. 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe.

For ex. var element = engine.createWebObject(1, 'a', 2); will create a WebObject element on Top level page with task id 1 and html tag 'a' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WebObject Once WebObject is created, you can play any one of the following event on it : ●

boolean click(); To replay a mouse click on element ❍

●

returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.click(); will replay click event on element. boolean rightClick(); To replay a mouse right click on element returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.rightClick(); will replay right click event on element. ❍

●

boolean dblClick(); To replay a mouse double click on element ❍

●


For ex. element.dblClick(); will replay double click event on element. boolean mouseMove(); To move mouse cursor over element returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.mouseMove(); will move mouse cursor on element. boolean wait(String propertyName, String propertyValue, long timeout); Will make replayer wait till specified property recieves specified value or till the specified time out period, whatever happens earlier, where ❍

●

'propertyName' name of the element's attribute for which the value should be fetched. ❍ 'propertyValue' value of the attribute against which the comparision should be done. ❍ 'timeout' in no. of seconds, time period for which the replayer should wait to get the expected value ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.wait('innerText', 'AppPerfect', 30); will make replayer to wait till innertext for this element is not equal to 'AppPerfect', maximum waiting time will be 30 seconds. If attribute does not receive the expected value in this time period then event will be marked as timed out. ❍

WebArea

A WebArea represents HTML element with tag 'area'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebArea : ●

Creation of a WebArea

●

ed events for a WebArea

Creation of a WebArea WebArea element can be created using createWebArea API of IScriptEngine interface. The return value is an instance of WebArea interface. ●

WebArea createWebArea(int id, int iElementType); where, ❍

'id' is the Task Id. It should be unique across the test.

'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebArea(1, 2); will create a WebArea element on Top level page with task id 1 and html tag 'area' ❍


ed events for a WebArea Once WebArea is created, you can play events on it. WebArea s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebButton A WebButton represents HTML element with tag 'button'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebButton : ●

Creation of a WebButton

●

ed events for a WebButton

Creation of a WebButton WebButton element can be created using createWebButton API of IScriptEngine interface. The return value is an instance of WebButton interface. ●

WebButton createWebButton(int id, int iElementType); where,

'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebButton(1, 2); will create a WebButton element on Top level page with task id 1 and html tag 'button' ❍


ed events for a WebButton Once WebButton is created, you can play events on it. WebButton s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebCheckBox A WebCheckBox represents HTML element with tag 'input' and type='checkbox'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebCheckBox : ●

Creation of a WebCheckBox

●

ed events for a WebCheckBox

Creation of a WebCheckBox WebCheckBox element can be created using createWebCheckBox API of IScriptEngine interface. The return value is an instance of WebCheckBox interface. ●

WebCheckBox createWebCheckBox(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebCheckBox(1, 2); will create a WebCheckBox element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebCheckBox Once WebCheckBox is created, you can play events on it. Apart from ed events for a WebObject, WebCheckBox also s following events:

●

boolean check(); To select the checkbox

●

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.check(); will select the check box. boolean unCheck(); To deselect a check box ❍

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.unCheck(); will deselect the checkbox. ❍

WebComboBox A WebComboBox represents HTML element with tag 'select'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebComboBox : ●

Creation of a WebComboBox

●

ed events for a WebComboBox

Creation of a WebComboBox WebComboBox element can be created using createWebComboBox API of IScriptEngine interface. The return value is an instance of WebComboBox interface. ●

WebComboBox createWebComboBox(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebComboBox(1, 2); will create a WebComboBox element on Top level page with task id 1 and html tag 'select' ❍


ed events for a WebComboBox Once WebComboBox is created, you can play events on it. Apart from ed events for a WebObject, WebComboBox also s following events: ●

String[] getItems(); To get all the items in the Combo box returns array of items For ex. element.getItems(); will return all the items in combo box. ❍

●

String getItem(int index); To get item at specified index, where ❍ ❍

'index' is the position of item in combo, starts at 0. returns item at index

●

For ex. element.getItem(1); will return the second element in the combo. int getItemsCount(); To get the item count in the Combo box

●

returns count of items in combo For ex. element.getItemsCount(); will return count of items in combo box. String[] getSelectedItems(); To get selected items in the Combo box

●

returns array of selected items in combo For ex. element.getSelectedItems(); will return all the selected items in combo box. boolean select(int index); To select item at specified index, where

❍

❍

❍ ❍

●

'index' is the position of item in combo, starts at 0. returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.select(1); will select the second element in the combo. boolean selectItem(String item); To select specified item in combo, where 'item' is the text representing the item to be selected. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectItem('AppPerfect'); will select 'AppPerfect' item in the combo. ❍

WebDivElement A WebDivElement represents HTML element with tag 'div'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebDivElement : ●

Creation of a WebDivElement

●

ed events for a WebDivElement

Creation of a WebDivElement WebDivElement element can be created using createWebDivElement API of IScriptEngine interface. The return value is an instance of WebDivElement interface. ●

WebDivElement createWebDivElement(int id, int iElementType); where, ❍


'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebDivElement(1, 2); will create a WebDivElement element on Top level page with task id 1 and html tag 'div' ❍


ed events for a WebDivElement Once WebDivElement is created, you can play events on it. WebDivElement s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebEdit A WebEdit represents HTML element with tag 'input' and type='text'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebEdit : ●

Creation of a WebEdit

●

ed events for a WebEdit

Creation of a WebEdit WebEdit element can be created using createWebEdit API of IScriptEngine interface. The return value is an instance of WebEdit interface. ●

WebEdit createWebEdit(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebEdit(1, 2); will create a WebEdit element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebEdit Once WebEdit is created, you can play events on it. Apart from ed events for a WebObject, WebEdit also s following events: ●

boolean set(String text); To set the specified text in the input text box, where ❍ ❍

'text' is the text to set in the edit box returns true if event was executed successfully, returns false if there is any failure during execution

●

For ex. element.set('AppPerfect'); will set 'AppPerfect' as text in the edit box. boolean submit(); To submit the form ❍


For ex. element.submit(); will submit the form.

WebFile A WebFile represents HTML element with tag 'input' and type='file'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebFile : ●

Creation of a WebFile

●

ed events for a WebFile

Creation of a WebFile WebFile element can be created using createWebFile API of IScriptEngine interface. The return value is an instance of WebFile interface. ●

WebFile createWebFile(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebFile(1, 2); will create a WebFile element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebFile Once WebFile is created, you can play events on it. Apart from ed events for a WebObject, WebFile also s following events: ●

boolean set(String text); To set the specified text as the file path, where

●

'text' is the file path to set ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.set('C:\\file.txt'); will set 'C:\\file.txt' as file path boolean submit(); To submit the form ❍

❍

returns true if event was executed successfully, returns false if there is any failure

during execution For ex. element.submit(); will submit the form.

WebHiddenField A WebHiddenField represents HTML element with tag 'input' and type='hidden'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebHiddenField : ●

Creation of a WebHiddenField

●

ed events for a WebHiddenField

Creation of a WebHiddenField WebHiddenField element can be created using createWebHiddenField API of IScriptEngine interface. The return value is an instance of WebHiddenField interface. ●

WebHiddenField createWebHiddenField(int id, int iElementType); where, ❍ ❍

'id' is the Task Id. It should be unique across the test. 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe.

For ex. var element = engine.createWebHiddenField(1, 2); will create a WebHiddenField element on Top level page with task id 1 and html tag 'input' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WebHiddenField Once WebHiddenField is created, you can play events on it. Apart from ed events for a WebObject, WebHiddenField also s following events: ●

boolean set(String text); To set the specified text in the element, where

●

'text' is the text to set in the element ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.set('AppPerfect'); will set 'AppPerfect' as text in the element. boolean submit(); To submit the form ❍

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.submit(); will submit the form. ❍

WebImage A WebImage represents HTML element with tag 'img'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebImage : ●

Creation of a WebImage

●

ed events for a WebImage

Creation of a WebImage WebImage element can be created using createWebImage API of IScriptEngine interface. The return value is an instance of WebImage interface. ●

WebImage createWebImage(int id, int iElementType); where, ❍


'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebImage(1, 2); will create a WebImage element on Top level page with task id 1 and html tag 'img' ❍


ed events for a WebImage Once WebImage is created, you can play events on it. WebImage s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebInputElement A WebInputElement represents HTML element with tag 'input'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebInputElement : ●

Creation of a WebInputElement

●

ed events for a WebInputElement

Creation of a WebInputElement WebInputElement element can be created using createWebInputElement API of IScriptEngine interface. The return value is an instance of WebInputElement interface.

●

WebInputElement createWebInputElement(int id, int iElementType); where, ❍ ❍


For ex. var element = engine.createWebInputElement(1, 2); will create a WebInputElement element on Top level page with task id 1 and html tag 'input' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WebInputElement Once WebInputElement is created, you can play events on it. Apart from ed events for a WebObject, WebInputElement also s following events: ●

boolean set(String text); To set the specified text in the element, where ❍

'text' is the text to set in the element

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.set('AppPerfect'); will set 'AppPerfect' as text in the element. ❍

●

boolean submit(); To submit the form returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.submit(); will submit the form. ❍

WebInputButton A WebInputButton represents HTML element with tag 'input' and type='button'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebInputButton : ●

Creation of a WebInputButton

●

ed events for a WebInputButton

Creation of a WebInputButton WebInputButton element can be created using createWebInputButton API of IScriptEngine interface. The return value is an instance of WebInputButton interface. ●

WebInputButton createWebInputButton(int id, int iElementType); where, ❍


'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebInputButton(1, 2); will create a WebInputButton element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebInputButton Once WebInputButton is created, you can play events on it. WebInputButton s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebInputImage A WebInputImage represents HTML element with tag 'input' and type='image'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebInputImage : ●

Creation of a WebInputImage

●

ed events for a WebInputImage

Creation of a WebInputImage WebInputImage element can be created using createWebInputImage API of IScriptEngine interface. The return value is an instance of WebInputImage interface. ●

WebInputImage createWebInputImage(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebInputImage(1, 2); will create a WebInputImage element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebInputImage Once WebInputImage is created, you can play events on it. WebInputImage s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebLink A WebLink represents HTML element with tag 'a'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebLink : ●

Creation of a WebLink

●

ed events for a WebLink

Creation of a WebLink WebLink element can be created using createWebLink API of IScriptEngine interface. The return value is an instance of WebLink interface. ●

WebLink createWebLink(int id, int iElementType); where, ❍


'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebLink(1, 2); will create a WebLink element on Top level page with task id 1 and html tag 'a' ❍


ed events for a WebLink Once WebLink is created, you can play events on it. WebLink s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebList A WebList represents ordered/unordered list HTML element. For ordered list tag is 'ol', while for unordered list tag is 'ul'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebList : ●

Creation of a WebList

●

ed events for a WebList

Creation of a WebList WebList element can be created using createWebList API of IScriptEngine interface. The return

value is an instance of WebList interface. ●

WebList createWebList(int id, int iElementType, boolean bOrdered); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. ❍ 'bOrdered' is true if its ordered list, false otherwise. For ex. var element = engine.createWebList(1, 2, true); will create a ordered WebList element on Top level page with task id 1 and html tag 'ol' ❍


ed events for a WebList Once WebList is created, you can play events on it. Apart from ed events for a WebObject, WebList also s following events: ●

String[] getItems(); To get all the items in the WebList ❍

returns array of items in list

●

For ex. element.getItems(); will return all the items in WebList. String getItem(int index); To get item at specified index, where

●

'index' is the position of item in list, starts at 0. ❍ returns item at index For ex. element.getItem(1); will return the second element in the list. int getItemsCount(); To get the item count in the WebList

●

returns count of items in WebList For ex. element.getItemsCount(); will return count of items in WebList. boolean submit(); To submit the form

❍

❍

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.submit(); will submit the form. ❍

WebListItem A WebListItem represents HTML element with tag 'li'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebListItem : ●

Creation of a WebListItem

●

ed events for a WebListItem

Creation of a WebListItem WebListItem element can be created using createWebListItem API of IScriptEngine interface. The return value is an instance of WebListItem interface. ●

WebListItem createWebListItem(int id, int iElementType); where, ❍


'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebListItem(1, 2); will create a WebListItem element on Top level page with task id 1 and html tag 'li' ❍


ed events for a WebListItem Once WebListItem is created, you can play events on it. WebListItem s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebField A WebField represents HTML element with tag 'input' and type=''. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebField : ●

Creation of a WebField

●

ed events for a WebField

Creation of a WebField WebField element can be created using createWebField API of IScriptEngine interface. The return value is an instance of WebField interface. ●

WebField createWebField(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebField(1, 2); will create a WebField element on Top level page with task id 1 and html tag 'input' ❍

In order to keep the changes in UI and script in sync with each other, the name of the variable has

to be 'element'

ed events for a WebField Once WebField is created, you can play events on it. Apart from ed events for a WebObject, WebField also s following events: ●

boolean set(String text); To set the specified in the field, where ❍

'text' is the text to set as in the field

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.set('AppPerfect'); will set 'AppPerfect' as in the field. ❍

●

boolean submit(); To submit the form ❍


For ex. element.submit(); will submit the form.

WebRadioButton A WebRadioButton represents HTML element with tag 'input' and type='radio'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebRadioButton : ●

Creation of a WebRadioButton

●

ed events for a WebRadioButton

Creation of a WebRadioButton WebRadioButton element can be created using createWebRadioButton API of IScriptEngine interface. The return value is an instance of WebRadioButton interface. ●

WebRadioButton createWebRadioButton(int id, int iElementType); where, ❍ ❍


For ex. var element = engine.createWebRadioButton(1, 2); will create a WebRadioButton element on Top level page with task id 1 and html tag 'input' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WebRadioButton

Once WebRadioButton is created, you can play events on it. Apart from ed events for a WebObject, WebRadioButton also s following events: ●

boolean select(); To select the Radio Button returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.select(); will select the radio button. ❍

WebResetButton A WebResetButton represents HTML element with tag 'input' and type='reset'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebResetButton : ●

Creation of a WebResetButton

●

ed events for a WebResetButton

Creation of a WebResetButton WebResetButton element can be created using createWebResetButton API of IScriptEngine interface. The return value is an instance of WebResetButton interface. ●

WebResetButton createWebResetButton(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebResetButton(1, 2); will create a WebResetButton element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebResetButton Once WebResetButton is created, you can play events on it. WebResetButton s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebSpan A WebSpan represents HTML element with tag 'span'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following

operations/events are ed for a WebSpan : ●

Creation of a WebSpan

●

ed events for a WebSpan

Creation of a WebSpan WebSpan element can be created using createWebSpan API of IScriptEngine interface. The return value is an instance of WebSpan interface. ●

WebSpan createWebSpan(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebSpan(1, 2); will create a WebSpan element on Top level page with task id 1 and html tag 'span' ❍


ed events for a WebSpan Once WebSpan is created, you can play events on it. WebSpan s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebSubmitButton A WebSubmitButton represents HTML element with tag 'input' and type='submit'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebSubmitButton : ●

Creation of a WebSubmitButton

●

ed events for a WebSubmitButton

Creation of a WebSubmitButton WebSubmitButton element can be created using createWebSubmitButton API of IScriptEngine interface. The return value is an instance of WebSubmitButton interface. ●

WebSubmitButton createWebSubmitButton(int id, int iElementType); where, ❍ ❍

'id' is the Task Id. It should be unique across the test. 'iElementType' possible values, 2 if element is on top level page, 3 if element is

present on subframe. For ex. var element = engine.createWebSubmitButton(1, 2); will create a WebSubmitButton element on Top level page with task id 1 and html tag 'input' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WebSubmitButton Once WebSubmitButton is created, you can play events on it. WebSubmitButton s exactly same events as WebObject. Please refer to ed events for a WebObject for more details.

WebTable A WebTable represents Table HTML element with tag 'table'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebTable : ●

Creation of a WebTable

●

ed events for a WebTable

Creation of a WebTable WebTable element can be created using createWebTable API of IScriptEngine interface. The return value is an instance of WebTable interface. ●

WebTable createWebTable(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebTable(1, 2, true); will create a WebTable element on Top level page with task id 1 and html tag 'table' ❍


ed events for a WebTable Once WebTable is created, you can play events on it. Apart from ed events for a WebObject, WebTable also s following events: ●

String getCellData(long row, long column); To get cell data at specified row and column,

where 'row' is the index of row in Table, starts at 0. ❍ 'column' is the index of column in Table, starts at 0. ❍ returns cell's data at row, column For ex. element.getCellData(1, 1); will return the cell's data at second row and second column in the Table. long getColumnCount(long row); To get the column count at specified row in the WebTable ❍

●

❍

'row' is the index of row in Table, starts at 0.

returns count of columns at specified row in WebTable For ex. element.getColumnCount(1); will return count of columns at second row in WebTable. ❍

●

long getRowCount(); To get the row count in the WebTable ❍

●

return count of rows in WebTable

For ex. element.getRowCount(); will return count of rows in WebTable. boolean submit(); To submit the form returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.submit(); will submit the form. ❍

WebTextArea A WebTextArea represents HTML element with tag 'textarea'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebTextArea : ●

Creation of a WebTextArea

●

ed events for a WebTextArea

Creation of a WebTextArea WebTextArea element can be created using createWebTextArea API of IScriptEngine interface. The return value is an instance of WebTextArea interface. ●

WebTextArea createWebTextArea(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebTextArea(1, 2); will create a WebTextArea element on Top level page with task id 1 and html tag 'textarea' ❍


ed events for a WebTextArea Once WebTextArea is created, you can play events on it. Apart from ed events for a WebObject, WebTextArea also s following events: ●

boolean set(String text); To set the specified text in the textarea, where ❍

'text' is the text to set in the textarea

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.set('AppPerfect'); will set 'AppPerfect' as text in the textarea. ❍

WebTextField A WebTextField represents HTML element with tag 'input' and type='textfield'. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebTextField : ●

Creation of a WebTextField

●

ed events for a WebTextField

Creation of a WebTextField WebTextField element can be created using createWebTextField API of IScriptEngine interface. The return value is an instance of WebTextField interface. ●

WebTextField createWebTextField(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWebTextField(1, 2); will create a WebTextField element on Top level page with task id 1 and html tag 'input' ❍


ed events for a WebTextField Once WebTextField is created, you can play events on it. Apart from ed events for a WebObject, WebTextField also s following events: ●

boolean set(String text); To set the specified text in the element, where

❍ ❍

●

'text' is the text to set in the element returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.set('AppPerfect'); will set 'AppPerfect' as text in the element. boolean submit(); To submit the form returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.submit(); will submit the form. ❍

WebBrowserElement To fire any event on a WebBrowser one need to create WebBrowserElement. Apart from Configuring properties for a Web element Task, Execution of a Web element task and Release of a Web element task, following operations/events are ed for a WebBrowserElement : ●

Creation of a WebBrowserElement

●

ed events for a WebBrowserElement

Creation of a WebBrowserElement WebBrowserElement element can be created using createWebBrowserElement API of IScriptEngine interface. The return value is an instance of WebBrowserElement interface. ●

WebBrowserElement createWebBrowserElement(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' should always be 1 for element on a WebBrowser. For ex. var element = engine.createWebBrowserElement(1, 1); will create a WebBrowserElement element on WebBrowser with task id 1. ❍


ed events for a WebBrowserElement Once WebBrowserElement is created, you can play events on it. WebBrowserElement s following events: ●

boolean back(); To move to previous page in the WebBrowser

●

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.back(); will move to previous page in WebBrowser. boolean home(); To move to home page in the WebBrowser ❍

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.home(); will move to home page in WebBrowser. boolean forward(); To move to next page in the WebBrowser ❍

●

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.forward(); will move to next page in WebBrowser. ❍

●

boolean refresh(); To refresh page in the WebBrowser ❍

●


For ex. element.refresh(); will refresh page in WebBrowser. boolean close(); To close WebBrowser returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.close(); will close WebBrowser. ❍

Configuring properties for a Web element Task Once a task is created, all its properties like think time, title, timeout period etc. can be initialised to proper values using appropriate apis exposed by individual tasks. Following APIs are ed for configuring properties of a Web/HTML element task. ●

void setThinkTime(int iThinkTime); where, 'iThinkTime' is wait time in no. of seconds for which the engine should wait before the task is actually executed. For ex. element.setThinkTime(10); will set think time to 10 seconds. ❍

●

void setIgnored(boolean bIgnore); where, 'bIgnore' whether task should be ignored during execution. Possible values are true if task should be ignored, false otherwise. For ex. element.setIgnored(false); will ignore execution of task. void setExactMatchForAttributesComparision(boolean bExactMatch); This method should be called to match all the attributes exactly as they are while finding the target element. Else only part of the string is used during comparision of attributes. where, ❍

●

'bExactMatch' is true if all the attributes for the event are to matched exactly as they are; false otherwise. For ex. element.setExactMatchForAttributesComparision(false); void setTitle(String sTitle); where, ❍

●

'sTitle' title for event on element For ex. element.setTitle('click on WebObject'); void setDomIndex(long lDomIndex); This method should be called to set the DOM index of the target HTML element on which event is executed. Where, ❍

●

❍

'lDomIndex' is DOM index of the target HTML element.

●

For ex. element.setDomIndex(27); void setOuterHtml(String outerHtml); This method should be called to set the outerHTML of the target HTML element. This is used for highlighting the recorded element in the Editor view. Where, ❍

●

'outerHtml' is outer html code of the target HTML element.

For ex. element.setOuterHtml('INPUT title="AppPerfect" maxLength=2048 size=55 name=corp_id'); void setBreakPoint(boolean bBreakPoint); In case breakpoint is set, test will wait for 's interruption before moving forward. where, 'bBreakPoint' is true if breakpoint should be set; false otherwise. For ex. element.setBreakPoint(false); will clear breakpoint. void addAttribute(String sAttributeName, String sAttributeValue, boolean bIgnore, boolean bValidate); Each Web Element has a set of attributes, which are used to find the desired element during execution. where, ❍

●

❍ ❍ ❍

'sAttributeName' is name of the attribute 'sAttributeValue' is value of the attribute 'bIgnore' is true if this attribute should be ignored during execution; false otherwise.

'bValidate' is true if this attribute should be validated; false otherwise. For ex. element.addAttribute('innerText', 'AppPerfect', false, false); ❍

If attribute is parameterised then the value for same should be fetched using following API of IScriptEngine ●

String getParameterValue(String name, String value, String parameterName, boolean beforeExecution); where, ❍ ❍ ❍ ❍

❍

'name' is name of the attribute 'value' is recorded value of the attribute 'parameterName' is name of the test parameter 'bBeforeExecution' to indicate whether the test parameter should be populated before the execution of the task returns resultant value of parameterisation

For ex. var arg0 = engine.getParameterValue('innerText', 'AppPerfect', 'testparam1', true);

Execution of a Web element task Once a task is initialised it should be executed to fetch and process the results. Invoking the ed API for any Web Element will result in execution of that particular event. Please refer to Types of Web Element and all its ed events for more details. For ex. To execute a click event on WebLink the code statement will be var successful = element.click();

Release of a Web element task Once a task is executed it is must to call release method to release all the opened resources. It takes care to release all the internal objects like ResultSet, Connection etc. if any. Also this method takes care of saving the response/images if any to disk. This method should be always called in the end after the execution of each task. It can be done using following API of IScriptEngine interface ●

void release(); For ex. engine.release(); will release Web element task.

Window element task A window element represents dialogs or window components. For furthur details on ed elements and APIs go though the points mentioned below : ●

Types of Window Element

●

Configuring properties for a Window element Task

●

Execution of a Window element task

●

Release of a Window element task

Types of Window Element Following types of Window elements are ed in Web Test. Out of them, WinObject is generic element and can be used to represent any element not in the list. Please go through following elements for futhur details related to creation of each type of element and events ed on them. ●

WinObject

●

WinApplet

●

WinButton

●

WinCalendar

●

WinCheckBox

●

WinComboBox

●

WinEdit

●

WinFlash

●

WinListBox

●

WinListView

●

WinMenu

●

WinRadioButton

●

WinScrollBar

●

WinSpin

●

WinStatic

●

WinStatusBar

●

WinTab

●

WinToolbar

●

WinTreeView


WinObject A WinObject represents a generic Window element. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinObject : ●

Creation of a WinObject

●

ed events for a WinObject

Creation of a WinObject WinObject element can be created using createWinObject API of IScriptEngine interface. The return value is an instance of WinObject interface. ●

WinObject createWinObject(int id, String sWindowClass, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'sWindowClass' is the Window class name used to identify element. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinObject(1, 'Edit', 1); will create a WinObject element on browser with task id 1 and window class 'Edit' ❍


ed events for a WinObject Once WinObject is created, you can play any one of the following event on it : ●

void captureImage(String sImageFilePath, boolean overrideExisting); Captures image of the

●

window object, where ❍ 'sImageFilePath' The complete file path where the captured image should be saved. ❍ 'overrideExisting' Whether to override the image if it already exists. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.captureImage('C:\\image1.jpeg', false);. boolean click(int x, int y); To replay a mouse click on element, where ❍ ❍ ❍

'x', is horizontal coordinate, relative to left client rect position of window 'y', is vertical coordinate, relative to top client rect position of window returns true if event was executed successfully, returns false if there is any failure during execution

●

For ex. element.click(24, 36); will replay click event on element. boolean rightClick(int x, int y); To replay a mouse right click on element, where

●

'x', is horizontal coordinate, relative to left client rect position of window ❍ 'y', is vertical coordinate, relative to top client rect position of window ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.rightClick(24, 36); will replay right click event on element. boolean dblClick(int x, int y); To replay a mouse double click on element, where ❍

❍ ❍ ❍


●

For ex. element.dblClick(24, 36); will replay double click event on element. boolean mouseMove(int x, int y); To replay a mouse move on element, where

●

'x', is horizontal coordinate, relative to left client rect position of window ❍ 'y', is vertical coordinate, relative to top client rect position of window ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.mouseMove(24, 36); will replay mouse move event on element. boolean drag(int x, int y); To replay a drag event on element, where ❍

❍ ❍

'x', is horizontal coordinate, relative to left client rect position of window 'y', is vertical coordinate, relative to top client rect position of window

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.drag(24, 36); will replay a drag event on element. boolean drop(int x, int y); To replay a drop event on element, where ❍

●

❍ ❍ ❍


For ex. element.drop(24, 36); will replay drop event on element. ●

boolean vScroll(int option, int item); Vertically scrolls an object that has embedded scrollbars, where ❍

'option', is a pre-defined constant indicating the direction and increment-type to scroll. Possible values are as follows : ■ ■ ■ ■ ■ ■

0 Scrolls X lines down, where X is specified by the item argument 1 Scrolls X lines up, where X is specified by the item argument 2 Scrolls X pages down, where X is specified by the item argument 3 Scrolls X pages up, where X is specified by the item argument 4 Scrolls to the top of Scrollbar 5 Scrolls to the bottom of Scrollbar

6 Scrolls to the position specified by the item argument 'item', this value specifies the quantity of lines or pages to scroll ■

❍

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.vScroll(1, 2); will scroll 2 lines up. ❍

●

boolean hScroll(int option, int item); Horizontally scrolls an object that has embedded scrollbars, where ❍

'option', is a pre-defined constant indicating the direction and increment-type to scroll. Possible values are as follows : ■ ■ ■ ■ ■ ■ ■

0 Scrolls X lines forwards, where X is specified by the item argument 1 Scrolls X lines backwards, where X is specified by the item argument 2 Scrolls X pages forwards, where X is specified by the item argument 3 Scrolls X pages backwards, where X is specified by the item argument 4 Scrolls to the beginning of Scrollbar 5 Scrolls to the end of Scrollbar 6 Scrolls to the position specified by the item argument

'item', this value specifies the quantity of lines or pages to scroll ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.hScroll(1, 2); will scroll 2 lines backwards. boolean type(String keyBoardInput, boolean isAlphaNumeric); Types the specified string in the object, where ❍

●

❍ ❍

'keyBoardInput' A String value. The text string to type. 'isAlphaNumeric' is true if text string represents a alphanumeric key, false otherwise

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.type('AppPerfect', false); will type 'AppPerfect' text in the object. boolean maximize(); Maximizes the window to fill the entire screen. ❍

●

❍


For ex. element.maximize(); ●

boolean minimize(); Minimizes the window to an icon. ❍

●


For ex. element.minimize(); boolean restore(); Restores the window to its previous size. returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.restore(); ❍

●

boolean activate(); Activates the window.

●

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.activate(); boolean close(); Closes the window. ❍

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.close(); ❍

●

boolean wait(String propertyName, String propertyValue, long timeout); Will make replayer wait till specified property recieves specified value or till the specified time out period, whatever happens earlier, where 'propertyName' name of the element's attribute for which the value should be fetched. ❍ 'propertyValue' value of the attribute against which the comparision should be done. ❍ 'timeout' in no. of seconds, time period for which the replayer should wait to get the expected value ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.wait('innerText', 'AppPerfect', 30); will make replayer to wait till innertext for this element is not equal to 'AppPerfect', maximum waiting time will be 30 seconds. If attribute does not receive the expected value in this time period then event will be marked as timed out. ❍

WinApplet A WinApplet represents window element with class 'SunAwtCanvas'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinApplet : ●

Creation of a WinApplet

●

ed events for a WinApplet

Creation of a WinApplet

WinApplet element can be created using createWinApplet API of IScriptEngine interface. The return value is an instance of WinApplet interface. ●

WinApplet createWinApplet(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinApplet(1, 2); will create a WinApplet element on Top level page with task id 1 and class 'SunAwtCanvas' ❍


ed events for a WinApplet Once WinApplet is created, you can play events on it. WinApplet s exactly same events as WinObject. Please refer to ed events for a WinObject for more details.

WinButton A WinButton represents window element with class 'Button'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinButton : ●

Creation of a WinButton

●

ed events for a WinButton

Creation of a WinButton WinButton element can be created using createWinButton API of IScriptEngine interface. The return value is an instance of WinButton interface. ●

WinButton createWinButton(int id, int iElementType); where, ❍ ❍

'id' is the Task Id. It should be unique across the test. 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe.

For ex. var element = engine.createWinButton(1, 2); will create a WinButton element on Top level page with task id 1 and class 'Button' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WinButton Once WinButton is created, you can play events on it. WinButton s exactly same events as WinObject. Please refer to ed events for a WinObject for more details.

WinCalendar A WinCalendar represents window element with class 'CalWndMain'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinCalendar : ●

Creation of a WinCalendar

●

ed events for a WinCalendar

Creation of a WinCalendar WinCalendar element can be created using createWinCalendar API of IScriptEngine interface. The return value is an instance of WinCalendar interface. ●

WinCalendar createWinCalendar(int id, int iElementType); where, ❍


'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinCalendar(1, 2); will create a WinCalendar element on Top level page with task id 1 and class 'CalWndMain' ❍


ed events for a WinCalendar Once WinCalendar is created, you can play events on it. WinCalendar s exactly same events as WinObject. Please refer to ed events for a WinObject for more details.

WinCheckBox A WinCheckBox represents window element with class 'Button'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinCheckBox : ●

Creation of a WinCheckBox

●

ed events for a WinCheckBox

Creation of a WinCheckBox WinCheckBox element can be created using createWinCheckBox API of IScriptEngine interface. The return value is an instance of WinCheckBox interface. ●

WinCheckBox createWinCheckBox(int id, int iElementType); where, ❍ ❍


For ex. var element = engine.createWinCheckBox(1, 2); will create a WinCheckBox element on Top level page with task id 1 and class 'Button' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WinCheckBox Once WinCheckBox is created, you can play events on it. Apart from ed events for a WinObject WinCheckBox also s following events : ●

boolean check(); To select the checkbox ❍

●


For ex. element.check(); will select the check box. boolean unCheck(); To deselect a check box returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.unCheck(); will deselect the checkbox. ❍

WinComboBox A WinComboBox represents window element with class 'ComboBox'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinComboBox : ●

Creation of a WinComboBox

●

ed events for a WinComboBox

Creation of a WinComboBox WinComboBox element can be created using createWinComboBox API of IScriptEngine interface.

The return value is an instance of WinComboBox interface. ●

WinComboBox createWinComboBox(int id, int iElementType); where, ❍


'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinComboBox(1, 2); will create a WinComboBox element on Top level page with task id 1 and class 'ComboBox' ❍


ed events for a WinComboBox Once WinComboBox is created, you can play events on it. Apart from ed events for a WinObject WinComboBox also s following events : ●

String[] getItems(); To get all the items in the Combo box

●

returns array of items For ex. element.getItems(); will return all the items in combo box. String getItem(int index); To get item at specified index, where ❍

❍ ❍

'index' is the position of item in combo, starts at 0. returns item at index

●

For ex. element.getItem(1); will return the second element in the combo. int getItemsCount(); To get the item count in the Combo box

●

returns count of items in combo For ex. element.getItemsCount(); will return count of items in combo box. String getSelectedItem(); To get selected item in the Combo box

●

returns selected item in combo For ex. element.getSelectedItem(); will return the selected item in combo box. boolean select(int index); To select item at specified index, where

●

'index' is the position of item in combo, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.select(1); will select the second element in the combo. boolean selectItem(String item); To select specified item in combo, where

❍

❍

❍

'item' is the text representing the item to be selected. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectItem('AppPerfect'); will select 'AppPerfect' item in the combo. ❍

WinEdit A WinEdit represents window element with class 'Edit'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinEdit : ●

Creation of a WinEdit

●

ed events for a WinEdit

Creation of a WinEdit WinEdit element can be created using createWinEdit API of IScriptEngine interface. The return value is an instance of WinEdit interface. ●

WinEdit createWinEdit(int id, int iElementType); where, ❍


'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinEdit(1, 2); will create a WinEdit element on Top level page with task id 1 and class 'Button' ❍


ed events for a WinEdit Once WinEdit is created, you can play events on it. Apart from ed events for a WinObject WinEdit also s following events : ●

boolean set(String text); To set the specified text in the Edit box, where 'text' is the text to set in Edit box. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.set('AppPerfect'); will set 'AppPerfect' in the Edit box boolean setCaretPos(int row, int column); Places the cursor at the specified point in the edit box, where ❍

●

'row' is the The zero-based row position (in lines) at which the insertion point is placed. ❍ 'column' is the The zero-based column position (in characters in the specified row) at which the insertion point is placed. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.setCaretPos(2, 3); will place cursor at 4th character in third line of Edit Box. ❍

●

boolean setSelection(int columnFrom, int columnTo); Selects text in the edit box, where ❍ ❍

'columnFrom' is the zero-based column at which the selection starts (in characters). 'columnTo' is the zero-based column at which the selection ends (in characters).

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.setSelection(2, 3); will select text from 3rd to 4th character. ❍

WinFlash A WinFlash represents window element with class 'MacromediaFlashPlayerActiveX'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinFlash : ●

Creation of a WinFlash

●

ed events for a WinFlash

Creation of a WinFlash WinFlash element can be created using createWinFlash API of IScriptEngine interface. The return value is an instance of WinFlash interface. ●

WinFlash createWinFlash(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinFlash(1, 2); will create a WinFlash element on Top level page with task id 1 and class 'MacromediaFlashPlayerActiveX' ❍


ed events for a WinFlash Once WinFlash is created, you can play events on it. WinFlash s exactly same events as WinObject. Please refer to ed events for a WinObject for more details.

WinListBox A WinListBox represents window element with class 'ListBox'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinListBox :

●

Creation of a WinListBox

●

ed events for a WinListBox

Creation of a WinListBox WinListBox element can be created using createWinListBox API of IScriptEngine interface. The return value is an instance of WinListBox interface. ●

WinListBox createWinListBox(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinListBox(1, 2); will create a WinListBox element on Top level page with task id 1 and class 'ListBox' ❍


ed events for a WinListBox Once WinListBox is created, you can play events on it. Apart from ed events for a WinObject WinListBox also s following events : ●

String[] getItems(); To get all the items in the Listbox

●

returns array of items For ex. element.getItems(); will return all the items in Listbox. String getItem(int index); To get item at specified index, where

●

'index' is the position of item in ListBox, starts at 0. ❍ returns item at index For ex. element.getItem(1); will return the second element in the ListBox. int getItemsCount(); To get the item count in the ListBox

❍

❍

❍

returns count of items in ListBox

●

For ex. element.getItemsCount(); will return count of items in ListBox. String[] getSelectedItems(); To get selected items in the ListBox

●

returns array of selected items in ListBox For ex. element.getSelectedItems(); will return the selected items in ListBox. boolean select(int index); To select item at specified index, where ❍

'index' is the position of item in ListBox, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.select(1); will select the second element in the ListBox. ❍

●

boolean selectItem(String item); To select specified item in ListBox, where ❍ ❍

'item' is the text representing the item to be selected. returns true if event was executed successfully, returns false if there is any failure during execution

●

For ex. element.selectItem('AppPerfect'); will select 'AppPerfect' item in the ListBox. boolean deSelect(int index); To deselect item at specified index, where

●

'index' is the position of item in ListBox, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.deSelect(1); will deselect the second element in the ListBox. boolean deSelectItem(String item); To deselect specified item in ListBox, where ❍

❍ ❍

●

'item' is the text representing the item to be deselected. returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.deSelectItem('AppPerfect'); will deselect 'AppPerfect' item in the ListBox. boolean selectRange(int fromindex, int toIndex); To select multiple items in a listbox, where 'fromindex' is the index of first item in the range to be selected, starts at 0. ❍ 'toIndex' is the index of last item in the range to be selected, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectRange(1, 5); will select the range from second element to sixth element in the ListBox. boolean selectRangeItem(String fromitem, String toItem); To select multiple items in a listbox based on item text, where ❍

●

'fromitem' is the first item in the range to be selected, starts at 0. ❍ 'toItem' is the last item in the range to be selected, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectRange('AppPerfect', 'Testing Tools'); will select the items in specified range in the ListBox. ❍

●

boolean extendSelect(int index); To select an additional item in multiselect list box, where 'index' is the position of additional item to be selected in ListBox, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.extendSelect(1); boolean extendSelectItem(String item); To select an additional item in multiselect list box, where ❍

●

'item' is the text representing the additional item to be selected. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.extendSelectItem('AppPerfect'); ❍

WinListView A WinListView represents windows list view control with class 'SysListView32'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinListView : ●

Creation of a WinListView

●

ed events for a WinListView

Creation of a WinListView WinListView element can be created using createWinListView API of IScriptEngine interface. The return value is an instance of WinListView interface. ●

WinListView createWinListView(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinListView(1, 2); will create a WinListView element on Top level page with task id 1 and class 'ListView' ❍


ed events for a WinListView Once WinListView is created, you can play events on it. Apart from ed events for a WinObject WinListView also s following events : ●

String[] getItems(); To get all the items in the ListView

●

returns array of items For ex. element.getItems(); will return all the items in ListView. String getItem(int index); To get item at specified index, where

●

'index' is the position of item in ListView, starts at 0. ❍ returns item at index For ex. element.getItem(1); will return the second element in the ListView. int getItemsCount(); To get the item count in the ListView

●

returns count of items in listview For ex. element.getItemsCount(); will return count of items in ListView. String[] getSelectedItems(); To get selected items in the ListView

❍

❍

❍

❍

returns array of selected items in ListView

●

For ex. element.getSelectedItems(); will return the selected items in ListView. boolean select(int index); To select item at specified index, where ❍

'index' is the position of item in ListView, starts at 0.

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.select(1); will select the second element in the ListView. ❍

●

boolean selectItem(String item); To select specified item in ListView, where

●

'item' is the text representing the item to be selected. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectItem('AppPerfect'); will select 'AppPerfect' item in the ListView. boolean deSelect(int index); To deselect item at specified index, where ❍

❍

'index' is the position of item in ListView, starts at 0.

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.deSelect(1); will deselect the second element in the ListView. ❍

●

boolean deSelectItem(String item); To deselect specified item in ListView, where

●

'item' is the text representing the item to be deselected. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.deSelectItem('AppPerfect'); will deselect 'AppPerfect' item in the ListView. boolean selectRange(int fromindex, int toIndex); To select multiple items in a ListView, where ❍

'fromindex' is the index of first item in the range to be selected, starts at 0. ❍ 'toIndex' is the index of last item in the range to be selected, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectRange(1, 5); will select the range from second element to sixth element in the ListView. ❍

●

boolean selectRangeItem(String fromitem, String toItem); To select multiple items in a ListView based on item text, where 'fromitem' is the first item in the range to be selected, starts at 0. ❍ 'toItem' is the last item in the range to be selected, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectRange('AppPerfect', 'Testing Tools'); will select the items in specified range in the ListView. boolean extendSelect(int index); To select an additional item in multiselect list box, where ❍

●

'index' is the position of additional item to be selected in ListView, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.extendSelect(1); ❍

●

boolean extendSelectItem(String item); To select an additional item in multiselect list box, where ❍ ❍

●

'item' is the text representing the additional item to be selected. returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.extendSelectItem('AppPerfect'); int getColumnCount(); To get the number of columns in the (report style) listview object. returns number of columns in the listview For ex. element.getColumnCount(); String getColumnHeader(int index); To get the text header of the specified (report style) listview column, where ❍

●

'index' is the zero-based index of the column ❍ returns column header text of specified column For ex. element.getColumnHeader(1); ❍

WinMenu A WinMenu represents windows menu bar. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinMenu : ●

Creation of a WinMenu

●

ed events for a WinMenu

Creation of a WinMenu WinMenu element can be created using createWinMenu API of IScriptEngine interface. The return value is an instance of WinMenu interface. ●

WinMenu createWinMenu(int id, String sWindowClass, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'sWindowClass' is the Window class name used to identify element. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinMenu(1, 'Notepad', 2); will create a WinMenu element. ❍


ed events for a WinMenu

Once WinMenu is created, you can play events on it. WinMenu s following events : ●

boolean selectItem(String menuPath, boolean isContextMenu, boolean selectByCommand); To select the specified menuitem, where ❍

❍ ❍

❍

●

'menuPath' specifies the complete path of the menu item, separate each item with a semicolon (;) 'isContextMenu' is true if its a context menu, false otherwise 'selectByCommand' is true if item should be selected using command identifier, false otherwise returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.selectItem('&Help;&About Notepad', false, true); will select the specified menu item boolean wait(String propertyName, String propertyValue, long timeout); Will make replayer wait till specified property recieves specified value or till the specified time out period, whatever happens earlier, where 'propertyName' name of the element's attribute for which the value should be fetched. ❍ 'propertyValue' value of the attribute against which the comparision should be done. ❍ 'timeout' in no. of seconds, time period for which the replayer should wait to get the expected value ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.wait('innerText', 'AppPerfect', 30); will make replayer to wait till innertext for this element is not equal to 'AppPerfect', maximum waiting time will be 30 seconds. If attribute does not receive the expected value in this time period then event will be marked as timed out. ❍

WinRadioButton A WinRadioButton represents window element with class 'Button'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinRadioButton : ●

Creation of a WinRadioButton

●

ed events for a WinRadioButton

Creation of a WinRadioButton WinRadioButton element can be created using createWinRadioButton API of IScriptEngine interface. The return value is an instance of WinRadioButton interface. ●

WinRadioButton createWinRadioButton(int id, int iElementType); where, ❍


'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinRadioButton(1, 2); will create a WinRadioButton element on Top level page with task id 1 and class 'Button' ❍


ed events for a WinRadioButton Once WinRadioButton is created, you can play events on it. Apart from ed events for a WinObject WinRadioButton also s following events : ●

boolean select(); To select the Radio Button ❍


For ex. element.select(); will select the radio.

WinScrollbar A WinScrollbar represents window element with class 'Scrollbar'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinScrollbar : ●

Creation of a WinScrollbar

●

ed events for a WinScrollbar

Creation of a WinScrollbar WinScrollbar element can be created using createWinScrollbar API of IScriptEngine interface. The return value is an instance of WinScrollbar interface. ●

WinScrollbar createWinScrollbar(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinScrollbar(1, 2); will create a WinScrollbar element on Top level page with task id 1 and class 'Scrollbar' ❍


ed events for a WinScrollbar Once WinScrollbar is created, you can play events on it. Apart from ed events for a WinObject WinScrollbar also s following events : ●

boolean set(int position); Sets the scroll bar position, where ❍ ❍

●

For ex. element.set(100); boolean nextLine(int count); Moves the scroll bar downward, or to the right by the specified number of lines, where ❍ ❍

●

'count' is number of lines to move returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.nextLine(1); boolean prevLine(int count); Moves the scroll bar upward, or to the left, by the specified number of lines, where ❍ ❍

●

'position' is scroll bar position to set returns true if event was executed successfully, returns false if there is any failure during execution

'count' is number of lines to move returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.prevLine(1); boolean nextPage(int count); Moves the scroll bar downward, or to the right by the specified number of pages, where 'count' is number of Pages to move ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.nextPage(1); boolean prevPage(int count); Moves the scroll bar upward, or to the left, by the specified number of Pages, where ❍

●

❍

'count' is number of Pages to move

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.prevPage(1); ❍

WinSpin A WinSpin represents window element with class 'msctls_updown32'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinSpin : ●

Creation of a WinSpin

●

ed events for a WinSpin

Creation of a WinSpin WinSpin element can be created using createWinSpin API of IScriptEngine interface. The return value is an instance of WinSpin interface. ●

WinSpin createWinSpin(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinSpin(1, 2); will create a WinSpin element on Top level page with task id 1 and class 'msctls_updown32' ❍


ed events for a WinSpin Once WinSpin is created, you can play events on it. Apart from ed events for a WinObject WinSpin also s following events : ●

boolean set(int position); Sets the spin object to the specified value, where ❍ ❍

'position' is value to set returns true if event was executed successfully, returns false if there is any failure during execution

●

For ex. element.set(100); boolean next(int count); Sets the spin object to its next value by specified count, where

●

'count' is count to move ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.next(1); boolean prev(int count); Sets the spin object to its previous value by specified count, where ❍

'count' is count to move ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.prev(1); ❍

WinStatic A WinStatic represents window element with class 'Static'. Apart from Configuring properties for a

Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinStatic : ●

Creation of a WinStatic

●

ed events for a WinStatic

Creation of a WinStatic WinStatic element can be created using createWinStatic API of IScriptEngine interface. The return value is an instance of WinStatic interface. ●

WinStatic createWinStatic(int id, int iElementType); where, ❍


'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinStatic(1, 2); will create a WinStatic element on Top level page with task id 1 and class 'Static' ❍


ed events for a WinStatic Once WinStatic is created, you can play events on it. WinStatic s exactly same events as WinObject. Please refer to ed events for a WinObject for more details.

WinStatusBar A WinStatusBar represents window element with class 'msctls_statusbar32'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinStatusBar : ●

Creation of a WinStatusBar

●

ed events for a WinStatusBar

Creation of a WinStatusBar WinStatusBar element can be created using createWinStatusBar API of IScriptEngine interface. The return value is an instance of WinStatusBar interface. ●

WinStatusBar createWinStatusBar(int id, int iElementType); where, ❍


❍

'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe.

For ex. var element = engine.createWinStatusBar(1, 2); will create a WinStatusBar element on Top level page with task id 1 and class 'msctls_statusbar32' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WinStatusBar Once WinStatusBar is created, you can play events on it. Apart from ed events for a WinObject WinStatusBar also s following events : ●

String[] getItems(); To get all the items in the StatusBar ❍

returns array of items

●

For ex. element.getItems(); will return all the items in StatusBar. String getItem(int index); To get item at specified index, where

●

'index' is the position of item in StatusBar, starts at 0. ❍ returns item at index For ex. element.getItem(1); will return the second element in the StatusBar. int getItemsCount(); To get the item count in the StatusBar ❍

returns count of items in StatusBar For ex. element.getItemsCount(); will return count of items in StatusBar. ❍

WinTab A WinTab represents window element with class 'SysTabControl32'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinTab : ●

Creation of a WinTab

●

ed events for a WinTab

Creation of a WinTab WinTab element can be created using createWinTab API of IScriptEngine interface. The return value is an instance of WinTab interface. ●

WinTab createWinTab(int id, int iElementType); where, ❍ ❍

'id' is the Task Id. It should be unique across the test. 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on

top level page, 3 if element is present on subframe. For ex. var element = engine.createWinTab(1, 2); will create a WinTab element on Top level page with task id 1 and class 'SysTabControl32' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WinTab Once WinTab is created, you can play events on it. Apart from ed events for a WinObject WinTab also s following events : ●

String[] getItems(); To get all the items in the Tab control

●

returns array of items For ex. element.getItems(); will return all the items in Tab control. String getItem(int index); To get item at specified index, where ❍

❍

'index' is the position of item in Tab control, starts at 0.

returns item at index For ex. element.getItem(1); will return the second element in the Tab control. ❍

●

int getItemsCount(); To get the item count in the Tab control ❍

returns count of items in Tab control

●

For ex. element.getItemsCount(); will return count of items in Tab control. String getSelectedItem(); To get selected item in the Tab control

●

returns selected item in Tab control For ex. element.getSelectedItem(); will return the selected item in Tab control boolean select(int index); To select item at specified index, where

●

'index' is the position of item in Tab control, starts at 0. ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.select(1); will select the second element in the Tab control. boolean selectItem(String item); To select specified item in Tab control, where

❍

❍

❍ ❍

'item' is the text representing the item to be selected. returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.selectItem('AppPerfect'); will select 'AppPerfect' item in the Tab control.

WinToolbar A WinToolbar represents window element with class 'ToolbarWindow32'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinToolbar :

●

Creation of a WinToolbar

●

ed events for a WinToolbar

Creation of a WinToolbar WinToolbar element can be created using createWinToolbar API of IScriptEngine interface. The return value is an instance of WinToolbar interface. ●

WinToolbar createWinToolbar(int id, int iElementType); where, ❍ ❍


For ex. var element = engine.createWinToolbar(1, 2); will create a WinToolbar element on Top level page with task id 1 and class 'ToolbarWindow32' In order to keep the changes in UI and script in sync with each other, the name of the variable has to be 'element'

ed events for a WinToolbar Once WinToolbar is created, you can play events on it. Apart from ed events for a WinObject WinToolbar also s following events : ●

String[] getItems(); To get all the items in the Toolbar control

●

returns array of items For ex. element.getItems(); will return all the items in Toolbar control. String getItem(int index); To get item at specified index, where ❍

❍ ❍

'index' is the position of item in Toolbar control, starts at 0. returns item at index

●

For ex. element.getItem(1); will return the second element in the Toolbar control. int getItemsCount(); To get the item count in the Toolbar control

●

returns count of items in Toolbar control For ex. element.getItemsCount(); will return count of items in Toolbar control. String getSelectedItem(); To get selected item in the Toolbar control

●

returns selected item in Toolbar control For ex. element.getSelectedItem(); will return the selected item in Toolbar control boolean select(int index); To select item at specified index, where

❍

❍

❍ ❍

'index' is the position of item in Toolbar control, starts at 0. returns true if event was executed successfully, returns false if there is any failure during execution

●

For ex. element.select(1); will select the second element in the Toolbar control. boolean selectItem(String item); To select specified item in Toolbar control, where ❍

'item' is the text representing the item to be selected.

returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectItem('AppPerfect'); will select 'AppPerfect' item in the Toolbar control. ❍

WinTreeView A WinTreeView represents window element with class 'SysTreeView32'. Apart from Configuring properties for a Window element Task, Execution of a Window element task and Release of a Window element task, following operations/events are ed for a WinTreeView : ●

Creation of a WinTreeView

●

ed events for a WinTreeView

Creation of a WinTreeView WinTreeView element can be created using createWinTreeView API of IScriptEngine interface. The return value is an instance of WinTreeView interface. ●

WinTreeView createWinTreeView(int id, int iElementType); where, 'id' is the Task Id. It should be unique across the test. ❍ 'iElementType' possible values, 1 if element is on a WebBrowser, 2 if element is on top level page, 3 if element is present on subframe. For ex. var element = engine.createWinTreeView(1, 2); will create a WinTreeView element on Top level page with task id 1 and class 'SysTreeView32' ❍


ed events for a WinTreeView Once WinTreeView is created, you can play events on it. Apart from ed events for a WinObject WinTreeView also s following events : ●

String[] getItems(); To get all the items in the TreeView control

●

returns array of items For ex. element.getItems(); will return all the items in TreeView control. int getItemsCount(); To get the item count in the TreeView control ❍

❍

returns count of items in TreeView control

●

For ex. element.getItemsCount(); will return count of items in TreeView control. String[] getSelectedItems(); To get selected items in the TreeView control ❍

●

returns array of selected items in TreeView control

For ex. element.getSelectedItems(); will return the selected items in TreeView control boolean selectItem(String nodePath); To select specified item in TreeView control, where 'nodePath' is the text representing the complete path of tree item to be selected. Each item is separated by a semicolon (;) ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.selectItem('AppPerfect;Web Test'); boolean collapse(String nodePath); To collapse the specified node in TreeView control, where ❍

●

❍

❍

●

'nodePath' is the text representing the complete path of tree item to be collapsed. Each item is separated by a semicolon (;) returns true if event was executed successfully, returns false if there is any failure during execution

For ex. element.collapse('AppPerfect;Web Test'); boolean expand(String nodePath); To expand the specified node in TreeView control, where 'nodePath' is the text representing the complete path of tree item to be expanded. Each item is separated by a semicolon (;) ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.expand('AppPerfect;Web Test'); boolean expandAll(String nodePath); To expand the specified node in TreeView control and all of the nodes below it, where ❍

●

'nodePath' is the text representing the complete path of tree item to be expanded. Each item is separated by a semicolon (;) ❍ returns true if event was executed successfully, returns false if there is any failure during execution For ex. element.expandAll('AppPerfect;Web Test'); ❍

Configuring properties for a Window element Task Once a task is created, all its properties like think time, title, timeout period etc. can be initialised to proper values using appropriate apis exposed by individual tasks. Following APIs are ed for configuring properties of a Window element task. ●

void setThinkTime(int iThinkTime); where,

●

'iThinkTime' is wait time in no. of seconds for which the engine should wait before the task is actually executed. For ex. element.setThinkTime(10); will set think time to 10 seconds. void setIgnored(boolean bIgnore); where, ❍

'bIgnore' whether task should be ignored during execution. Possible values are true if task should be ignored, false otherwise. For ex. element.setIgnored(false); will ignore execution of task. void setRecordedWhileShowingSSLCertificate(boolean flag); This method should be called to mark event as an event on SSL certificate dialog. where, ❍

●

'flag' is true if this event is an event on SSL certificate dialog; false otherwise. For ex. element.setRecordedWhileShowingSSLCertificate(false); ❍

●

void setTitle(String sTitle); where, 'sTitle' title for event on element For ex. element.setTitle('click on WinObject'); void setImagePath(String sImagePath); This method should be called to set the element's image path. This is used for showing the elements image in the Editor view. Where, ❍

●

'sImagePath' is file path of the element's image saved on disk. Path is relative to the project location. For ex. element.setImagePath('recorded/2006_12_1_13_39_1_50/ActionGroup1/ appftimage0.jpeg'); ❍

●

void setBreakPoint(boolean bBreakPoint); In case breakpoint is set, test will wait for 's interruption before moving forward. where, 'bBreakPoint' is true if breakpoint should be set; false otherwise. For ex. element.setBreakPoint(false); will clear breakpoint. void addAttribute(String sAttributeName, String sAttributeValue, boolean bIgnore, boolean bValidate); Each Window Element has a set of attributes, which are used to find the desired element during execution. where, ❍

●

'sAttributeName' is name of the attribute ❍ 'sAttributeValue' is value of the attribute ❍ 'bIgnore' is true if this attribute should be ignored during execution; false otherwise. ❍ 'bValidate' is true if this attribute should be validated; false otherwise. For ex. element.addAttribute('windowIndex', '1', false, false); ❍

If attribute is parameterised then the value for same should be fetched using following API of IScriptEngine ●

String getParameterValue(String name, String value, String parameterName, boolean beforeExecution); where, 'name' is name of the attribute ❍ 'value' is recorded value of the attribute ❍ 'parameterName' is name of the test parameter ❍ 'bBeforeExecution' to indicate whether the test parameter should be populated before the execution of the task ❍ returns resultant value of parameterisation For ex. var arg0 = engine.getParameterValue('windowIndex', '1', 'testparam1', true); ❍

Execution of a Window element task Once a task is initialised it should be executed to fetch and process the results. Invoking the ed API for any Window Element will result in execution of that particular event. Please refer to Types of Window Element and all its ed events for more details. For ex. To execute a click event on WinObject the code statement will be var successful = element.click(24,36);This will simulate a mouse click at specified coordinates. The coordinates are relative to the top left client rect of the window.

Release of a Window element task Once a task is executed it is must to call release method to release all the opened resources. It takes care to release all the internal objects like ResultSet, Connection etc. if any. Also this method takes care of saving the response/images if any to disk. This method should be always called in the end after the execution of each task. It can be done using following API of IScriptEngine interface ●

void release(); For ex. engine.release(); will release Window element task.

Validating a task response To determine whether a task has executed successfully or not you need to validate the data received in the response. This chapter will cover: ●

Validating a Web task

Validating a Web task A web task is web request with either http for simple request or https for secured request. When a web task is executed we get WebResponse, you can validate this WebResponse using following APIs. You can also write your custom functions apart from following standard functions provided to do custom validation and can set the status of task based on that. ●

●

●

●

●

●

●

●

●

●

●

WebResponse getWebResponse(); Once the task is executed, this method returns the contents of the response received. This can be null whenthere is no response from the server, typically when the request is re-directed to some other URL or the server, requests for authentication information etc. boolean isValidationSuccessful(); Once the task is executed, this method returns the status of the validation carried out. void setValidationSuccessful(boolean success); Once the task is executed, this method can be used to set the status of validation. IValidationResult getValidationResult(); Once the task is executed, detailed validation result can be fetched using this method. boolean assertNodeText(String description, String nodePath, String text); Once the task is executed, text of the node in the DOM tree of the response data can be validated. boolean assertNodeAttributeValue(String description, String nodePath, String attributeName, String attributeValue); Once the task is executed, attributes of the node in the DOM tree of the response data can be validated. boolean assertInDatabase(String description, String databaseId, String query); Once the task is executed, database can be validated by firing the specified SELECT query. boolean assertTodaysDate(String description, String dateFormat, String prefix, String suffix); Once the task is executed, response can be validated to contain today's date in specified format. boolean assertTodaysDate(String description, String dateFormat); Once the task is executed, response can be validated to contain today's date in predefined format. boolean assertText(String description, String[] txt, boolean bCaseSensitive, boolean contains, boolean bAll, boolean checkForExistance, boolean regularExpression, String prefix, String suffix); Once the task is executed, response can be validated for presence/ absence of some text along with other attributes for fine-tuning the search. boolean assertText(String description, String txt, boolean bCaseSensitive, boolean checkForExistance, boolean regularExpression, String prefix, String suffix); Once the task is

●

●

●

●

●

●

●

●

executed, response can be validated for presence/absence of some text along with other attributes for fine-tuning the search. boolean assertText(String description, String[] txt, boolean bCaseSensitive, boolean contains, boolean bAll, boolean checkForExistance, boolean regularExpression); Once the task is executed, response can be validated for presence/absence of some text along with other attributes for fine-tuning the search. boolean assertText(String description, String txt, boolean bCaseSensitive, boolean checkForExistance, boolean regularExpression); Once the task is executed, response can be validated for presence/absence of some text along with other attributes for fine-tuning the search. boolean assertPage(String description); Once the task is executed, the response page can be validated using this method. boolean assertLinkCount(String description, int count); Once the task is executed, no of links in the response can be validated using this method. boolean assertFormCount(String description, int count); Once the task is executed, no of forms in the response can be validated using this method. boolean assertImageCount(String description, int count); Once the task is executed, no of images in the response can be validated using this method. boolean assertInputElementCount(String description, int count); Once the task is executed, no of input elements in the response can be validated using this method. boolean assertPageSize(String description, long sizeInBytes); Once the task is executed, size of the response can be validated using this method.

Appperfect Web Test 426f3e

Overview 4q3b3c

More details 26j3b

Related Documents 171j1w

Appperfect Web Test 426f3e

Practical Web Test Automation 3s591q

Simply Cae Test 1 Web 546b61

Web 2e4w4c

Web 2e4w4c

Web 2e4w4c

More Documents from "AppPerfect Corporation" 5331g

Appperfect Web Test 426f3e

2c82t

Vdi Proof Of Concept (poc) Test Plan t5f4f

Ems Kenya Product And Tariff Guide d1k2t

Jackson Industries Fluoropolymer Hose Catalog 1j683k

Pertua Marketing Corporation Company Profile 5i4l58