The Tools -> Options dialog box lets you specify a number of important properties to control Web Test behavior. Properties configured here are applied to all the projects in the test. Following is a description of the various tabs and properties found in them.
Number of Recent Project Files: Specify the number of project files to show in the most recently used menu list. The default is 5.
Number of Recent Result Files: Specify the number of result files to show in the most Recently used menu list. The default is 5.
Highlight Row/node on mouse over:This setting is for highlighting the current row you are browsing or the current node you are visiting in AppPerfect product.
Save Result: Define your results-save strategy here. You can configure to save result for each project run automatically or to save just last run of the project. Default value is to not save result automatically.
User Name: Shows the name of the user configured in AppPerfect Test Manager. Multiple users can be configured with AppPerfect Test Manager and each client AppPerfect product can use unique user name to submit results/ projects to Test Manager. This user name is used as identifier and is helpful in generating user based reports in Test Manager. In case connection to Test Manager is not configured Or if there is only single user configured in Test Manager then this field is un-editable.
To control the memory usage of application during execution you can configure Garbage collector settings here. AppPerfect takes care of forcing the garbage collection once the specified limit is reached. You can also configure how often AppPerfect should check for memory consumption.
You can set your own font for AppPerfect Web Test.
Application can be configured to check for new updates/release of the AppPerfect product. On finding one application notifies the user about the availability of same. Keeping this feature enabled ensures that you are using latest version of the product.
AppPerfect supports recording/replaying of test on multiple browsers including Internet Explorer, Firefox and Safari Here you can configure browser which application should use to perform recording/replaying. The one selected as default is used for recording/replaying of the test. AppPerfect also uses the browser configured here to open Help files and exported results/reports. You should have proper browser configured for application to work correctly.
Specify your JDK's name and path here. AppPerfect will use the default JDK specified at the time of installation. You may want to use other JDKs for your applications and those can be defined and used from here.
You can configure Database related properties like Database name, Connection URL, JDBC driver, User Name, password etc. here. This is useful in case you need to fetch values from database to parameterize your test. Database configuration is also required in case you need to add Database validation in test.
In case your application uses a custom SSL certificate (i.e. certificate not provided by Verisign or Thawte), then either you need to make that custom certificate trusted by the JVM running AppPerfect product or you may select the option to "Accept Self-signed or untrusted custom SSL certificates."
To make the custom certificate trusted by the JVM running AppPerfect product, you need to add the SSL certificate here. AppPerfect uses this certificate when running your test. Certificates provided by Verisign or Thawte are automatically trusted by the "trust file" within the JVM. All other certificates are considered custom SSL certificates. If you are using a Custom certificate, you will need to import that certificate into AppPerfect. In case you don't have the certificate file, open your HTTPS link in a browser and then click on the "lock" icon. This will pop up a dialog box with "Certificate" title & General tab selected. Go to Details tab and select "Copy to File..." option. Proceed with the wizard. On Export file format select "Base-64 encoded..." radio button. Save it to some temporary location and import this certificate file. Please note that you will be required to restart AppPerfect product after registering custom certificate.
If error occurs during test run: Select the option that best suits your requirement for errors. You can configure to stop test run, ignore error and continue with next task or group, you can also configure to prompt for user action in case error occurs and can also retry the execution of the erroneous task during runtime.
Auto Detect mouse-over events on elements having mouse-over event handlers: By default, application does not record mouse-over events on elements which does not have mouse-over event selected. If you have a web page which uses mouse-over event to do certain action, for example, in DHTML menu bars, where on mouse-over, menu opens into sub-menus, then you should select this check box. If this checkbox is selected then during recording application tries to find the mouse over event handlers on the fly and records the mouse over event for the element which has mouse over event handler associated with it.
Use low level apis to replay mouse events on HTML elements: This option is valid only in case you are using Internet Explorer browser on Windows. By default application uses Web HTML apis to replay mouse events, but in some cases you may have underlying event handlers execute only if mouse cursor is hovered over the target element, like opening of a drop down menu or validation of form on mousedown/mouseup etc. In such cases you should select this option for replaying mouse events on HTML elements. In this case application uses Low level mouse events during execution of events and moves cursor to centre of target HTML element while replaying.
Use Accessibility to record window events: Events on window elements can be recorded in two ways, One by using Window's accessibility framework and recording accessible path to the UI element and other by using standard window enumeration to find the window component. Windows accessiblity provides more control over the nested UI elements in the UI heirarchy and this option should be used for recording on flash/flex or any custom controls. But this requires that the target custom control should implement the standard Accessible framework. All the window controls implements the accessible framework. This option should not be used in case the UI elements in your application changes its position in the UI heirarchy resulting in change of accessible path during each run.
Save all frames: By default application only saves those frames or pages on which event is recorded and does not save all the containing frames in the target web page. In case you need application to save all the subframes in your application then select this option. Useful in case you need to add validation on subframes in your application.
Perform strict attributes comparision to find element during replaying: During replaying application uses a search algorithm to find the desired html element on the target web page. By default application first tries to find the element at recorded element position also know as "tagIndex" for ex. 5th link or 6th input textbox. It then compares the recorded attributes/properties of the element against the one it finds from element at recorded tag index. Now if some of the attributes does not match then application by default tries to find the matching element with maximum number of matching attributes in the vicinity of the recorded tag position. This is to automatically handle cases where attributes of element changes dynamically during each run or where element position changes during each run. To change this default behaviour of searching element in the web page you can configure to "Perform strict attributes comparision to find element during replaying", where application will find the element only at recorded tag position and will strictly compare all the attributes of the element and in case it fails to match any attribute will report it as a failure. You should use this option in case you have static Web application where attributes and tag position of elements are not changing dynamically.
Record drag/drop event if mouse is dragged by more than N pixel: By default application records drag/drop event for window components only if mouse is dragged by more then 10 pixels. In case you need to increase/decrease this range, same can be edited here.
Elements on your Web page may have certain attributes that change dynamically for certain events, for example, the 'src' attribute of the 'img' element changing dynamically on mouseover. In this case, you should add this attribute to the list of 'Dynamically changing attributes' because otherwise the replayed test is likely to fail as there will be a mismatch in the recorded and replayed element. 'Src' and 'oSrc' attributes are already added to this list by default. You can add more by clicking the add button. All the attributes added to this list will be marked as ignored while recording the test.
All the Web or HTML elements that can be recorded by AppPerfect Web Test are configured here. You can select the ones you need for testing your web application. You can also add new elements and modify/delete the existing ones from here. AppPerfect is set to record the most commonly used elements and events on your Web page. However, if you find certain elements or events on your Web pages are not getting recorded, then first check if you have that specific HTML element configured here and has the corresponding event enabled for same. If you find that element is not present then you should add new HTML element having the same tag name as the html element you need to record and enable the events you need it to listen to. You can either check the HTML source of your web page to find the Tag name of the element or can use AppPerfect's Object Spy feature to find the tag name of the element.
License related settings are done here. You can configure license for either single client machine or can configure the product to pick the license from Floating license server in case you have purchased Floating license. Floating licenses are managed using License Manager in AppPerfect Test Manager.
AppPerfect maintains logs of fatal exceptions for all the products. You can change this setting here to log all messages. This option is very useful for debugging purposes. It is recommended that you use this feature in case you are facing any issues with the product and send us the log files. By default log files are saved at: <AppPerfect_Home>/logs. You can configure to change the log path and save logs at different location. Application can also log the values from the test script. For each log statement in test script you will find output getting logged in script_log.txt. The script log can be used to check the values getting used during parameterized test.
In case you are using Internet Explorer as the browser to record and replay and are not recording script for AppPerfect Load Test simultaneously then you do not need to configure these settings. Application provide the feature to simultaneously record script for AppPerfect Load Test while you are recording your Web Test. Also in case you are using Mozilla Firefox or Safari on MAC OSx or any other browser then you require to configure your proxy server settings to properly record and replay test. Refer to Proxy Recording chapter for more details.
AppPerfect starts its local proxy server and sets same in target browser. By default Application uses localhost and port 8690 to start the local proxy server. In case default port is in use by some other application you can change it to some other value here.
AppPerfect can automatically launch and configure proxy settings in your web browser wherever possible. If you want to do that yourself, deselect the checkbox 'Automatically launch and configure browser for recording.'
These settings are required if you do not have a direct connection to the Internet and you normally use a proxy server to access your application. The browser's current proxy settings have to be specified here. By default AppPerfect assumes a direct connection to the Internet.
These settings are required in case of Proxy Recording. All the patterns which are marked as excluded here are not recorded while recording. Application by default adds common update services installed on machine which are not part of your application and these requests should be dropped while recording tests. You can extend this list to add more patterns which you would like to exclude during recording.
AppPerfect Test Manager settings are done here. AppPerfect Test Manager provides functionality of requirement, project, results and issues management. It allows to schedule various project executions, view results, export them to various formats, add/manage test requirements and add/manage issues in the product. AppPerfect Test Manager by default runs on port 8744 and can be accessed as http://HOST_NAME:8744/AppTestManager.
Product related service settings are configured here. Each Web Test product also installs a product service which listens to requests from other Web Test product installations on remote machines while performing remote execution. This service by default runs on port 8854 and can be accessed as http://HOST_NAME:8854/AppService
AppPerfect Repository Settings is required to share AppPerfect projects across the team. AppPerfect provides support for Subversion(SVN) server for sharing projects across team. AppPerfect Repository server by default runs on port 8747 and can be accessed as svn://HOST_NAME:8747/AppRepository in case repository is created with "AppRepository" as the root folder. For complete details on configuration of Team or Repository Server refer to Team Server Configuration