|
|
QEngine's Web Functional Test settings section lets you configure and manage certain variables/parameters during runtime. The following play settings can be configured:
How do I get to the Settings screen?
From the Web Functional Test UI, select any suite name listed in the left-side panel and click the 'Settings' link from the screen displayed on the right side. You can also click the 'Settings' option listed under the suite name from the left-side tree itself. Both these actions will take you to the 'Settings' screen. From this screen, you can configure variables as explained below.
From the left pane in the Settings page, choose the Replay Settings tab to configure the replay options, wait time and mouse capture mode.
Replay Speed - To play the recorded web test cases with the same speed as that of recording time, select "Normal - User recorded speed". To play the recorded web test cases as fast as possible so that as soon as one task is over the other one starts immediately, select "Fast - Run as fast as possible".
Maximum wait time for document ready - Set the maximum time in seconds which will be taken as the maximum timeout value for the recorded actions in the script, so that while replaying the script the control does not wait indefinitely.
Wait for element - You can select this option if your applications create elements dynamically during runtime. Select the use wait for element checkbox and specify the wait time in seconds.
Mouse Capture mode - Here you can specify the mouse capture mode during runtime. If you select the 'True' option, QEngine will move the mouse over the element before a click. The mouse capture mode is applicable only for IMG, DIV, SPAN, LI, CELL and LINK elements. If you select the 'False' option, QEngine will click the element in the background without using the mouse.
In this screen, you can configure filters for scripts as well as use the Sequence Editor to change the sequence of recorded script execution. Click the 'Filter Configuration' link to open up the Filter Configurator screen where you can configure filters to execute scripts matching specific criteria.
Refer this page for detailed steps on configuring filters.
The Sequence Editor helps you configure the sequence in which test scripts need to be executed. Click the 'Sequence Editor' link to open the 'Sequence Editor' screen where you can specify the sequence of test scripts.
Refer this page for detailed steps to choose the order in which test scripts are executed..
From the left pane in the Settings page, choose the Exception Handling tab to handle the unexpected exceptions during playback using the following options.
Unexpected PopUp Exceptions
|
Type |
Purpose |
|---|---|
|
Report & Continue Play |
The exception message will be logged in the log file present under <QEngine Home/projects/<project name>/weblogs/testout.txt. It will be displayed in the log panel. Then, webscript execution will continue.
Also, this exception will be displayed in the Test results report. |
|
Stop Play |
The webscript execution will be stopped. |
|
Capture Screen & Continue Play |
Screen shot of the displayed window will be automatically taken and the picture file will be stored in <QEngine Home/projects/<project name>/webreports/screenshots folder. |
|
Close & Continue Play |
The dialog/alert window that has popped up will be closed and webscript execution will continue. |
|
Call Script |
To call another script when the dialog/alert window has
popped up. Enter the script name and script path to call the required
script. |
| Accept Dialog |
To press "OK" in any of
alert/confirm/prompt dialog encountered during play and procceed with
the further script playback. |
| Cancel Dialog |
To press "Cancel" in any of
the alert/confirm/prompt dialog encountered during play and proceed
with the further script playback. |
Web Exceptions
| Type |
Purpose |
|---|---|
|
Report& Continue Play |
The exception message will be logged in the log file present under <QEngine Home/projects/<project name>/weblogs/testout.txt. It will be displayed in the log panel. Then, webscript execution will continue.
Also, this exception will be displayed in the Test results report. |
|
Stop Play |
The webscript execution will be stopped. |
|
Call Script |
To call another script when the dialog/alert window has popped up. Enter the script name and script path to call the required script. |
Error Handling
When you get any Object exceptions related to the HTML objects in the page under recording such as ELEMENT_NOT_FOUND, then you can call another script using the Call Script option. Enter the script name and script path to call the required script.
This settings is valid for
regression playback. This is to reduce memory footprint of the playback
and to recover the playback if play hangs due to unhandled error.
Scritp Thershold - On completing the given number of scripts, the
browser will be restarted to minimize the memory footprints during
playback.
Response Timeout - During playback, if the browser does not responds to
the server for the configured timeout period, then QEngine determines
that the browser is in "Not Responding" mode and close all the browser
launched during playback and restart the test execution from the next
script in the suite.
Rerun Script - If the browser crashes intermittently you can choose the
option to rerun the currently executing script. This will be valid only
for regression testing.
If the option is enabled
the script currently under playback will be executed again.
If the option is not enabled
then the next script will be invoked and played back.
To email the failed test cases to selected recipients, from the left pane in the Settings page, choose the E-Mail Notification tab.
Select "Notify test case and script failures via e-mail" and "File Reports to Bug-Tracker" check boxes. Click on "Configure Mail Server Details" link to configure the mail server details. To know the details of configuring the mail server, please refer to the sub-topic Issue Tracking in the Suite Configuration page. The failed web test cases will be notified to the specified user through e-mail.
Send Summary Report
Click on the Send summary reports check box option to send the summary reports generated for web functional test execution to the specified recipients.
To test or playback the Web applications in the desired locale (to support internationalization), choose the Locale Settings tab from the left pane in the Settings page. From the right pane, select the Local Settings checkbox and choose the required language and country from the Language and Country combo boxes respectively. Click the link I18N Editor to edit the "<Suite_Name>"EnglishToNative_"<language_country>".properties file for the selected suite, language and country and specify the appropriate property values for the keys in the map file. To know the details of configuring the same, please refer to the topic Internationalization.
From the left pane in the Settings page, choose the Recorder Settings tab to configure the following options:
Use Suite Level
GUI Map - To use a global map
file for the entire suite, check the Use
Suite Level GUI
Map option. This mode creates a global map file for the entire
Suite. The global map file is placed in <QEngine_Home>/projects/<Suite_Name>/conf
directory. Note that in this case useLocalMapFile()
command is not embedded in the webscript.
Include Comment for each function - Enabling
this will allow script recorder to add help comment to each actions
that is getting recorded. The comment will be added during Recording, Adding Built-in functions,
Adding Checkpoints and Data Configuration. These auto
generated comments can be removed using the script by clicking "Remove
Auto Genarated Comments" link present below the script editor.
Enable Script Syntax Highlighting
-
Enabling this will allow script editor to give different color to the
each functions in the script. Disabling this will show the scripts
without color highlighting in the script editor.
Maximum wait time for mouseover recording - This is the maximum time upto which QEngine WebTest waits to record the mouseover event i.e., the mouseover events are recorded in the webscript only if the user places the mouse over a particular HTML object for more than the configured wait time. The default wait time for recording mouseover events is 2 seconds. You can configure the appropriate value as per your requirement.
You can select the elements for which
mouseover event needs to be recorded from the Record Mouse Over for the elements
list box. The elements supported include OL, UL, LI, TD, DIV, SPAN, A,
IMG and IMAGE.
Use System Wide Hook For Recording - This will enable system
wide hook during recording. This needs to be used only when it is
necessary. Normally QEngine will be able to record all the application
window. In some case if QEngine cannot record certain scenario, you can
enable this settings to make QEngine able to record the actions over
application window.
Note:
(Causes of enabling system wide hook)
This will slowdown the system
little bit.
This will crash Microsoft Outlook
application. Hence this needs to be used cautiously.
Click the Suite Customizer tab from the left pane in the Settings page to open the Suite Customizer page. Here you can configure suite customizations such as Severity, Report and Bug Tracker options. Refer this page for detailed steps.
From the left pane in the Settings page, choose the Host-Port Settings tab to dynamically change the host and port configurations and replay a single script against any server or port.
Assume you have multiple scripts in a suite where the recorded URLs in each of the script include the host and port details such as launchApplication("http://test-server:8080/homepage/index.html",2). To test the scripts with different host name and port number, you need to manually change the host and port number in all of these recorded URLs which will be a tedious task. To ease this process, you can use the Host-Port Settings UI to specify the new host name and port number to be tested. This will dynamically fetch the configured host name and port number and replays the script without re-recording.
To enable this option,
Select the check-box "Use Host-Port Configuration".
Click on the Host-Port Editor link.
In the Host Port Editor UI, click the New button placed next to the File Name combo. This will display a dialog that prompts to specify a property file name. Enter a file name in which the configured host and port details has to be stored and click the OK button. This will populate the newly created property file name in the combo.
Click the '+' sign placed before the Host label. This will add a new row in the table.
From the Old Protocol field, select the existing protocol (HTTP or HTTPS) used in the recorded URL.
From the New Protocol field, select the new protocol (HTTP or HTTPS) using which the scripts has to be replayed.
If you have newly recorded a script then the value for the Old Host field will be automatically populated. If you are trying to change the host for an existing sample script or for a script migrated from previous version to the current version then the Old Host field will be left empty. Here, you need to specify the existing host name.
In the New Host field, enter the new host name to be fetched dynamically and replayed.
If you have newly recorded a script then the value for the Old Port field will be automatically populated. If you are trying to change the port for an existing sample script or for a script migrated from previous version to the current version then the Old Port field will be left empty. Here, you need to specify the existing port number.
In the New Port field , enter the new port number to be fetched dynamically and replayed.
Click the Apply button to save the changes. You can add more configurations by clicking the '+' sign placed before the Host label.
To delete a particular configuration, click the delete image in the corresponding row to be deleted.
Click the Apply button to save the changes.
To close the UI, click the Close button.
The above configuration will dynamically replace the protocol and fetch the configured host name and port number to replay the recorded URLs with the specified values.
|
|
Note: To change only the host name, specify the new host name in the New Host field and the existing port number (since there is no change in the port number) in the New Port field which will be taken as a name-value pair. Then, click the Apply button to save the changes. Since the host name and port number is taken as a name-value pair, if you are not specifying the port no, then the configured host name will not be considered during playback. |
|
|
