- Runtime parameters of test script
- Running a script in secure mode
- Running a script several times in a row
- Modifying the execution duration
- Specifying a time-out between each operation
- Checking the execution of test script
- Playing a test script in continuous mode
- Playing a test script step by step
WDTest : Running a test script
From version 26
, the WDTest utility is no longer available.
WDTest is used to run the test scripts:
- continuously. The entire script is played. A check is performed at the end. See Checking the execution of test script for more details.
- step by step. You can run:
- the script events one by one,
- a set of script events,
- the entire script.
This feature is used to find out the execution result of one or more events.
When running an event, a set of events or the entire test script, a result test script (".LOG" file) is generated. This text file contains the description of operations performed.
Runtime parameters of test script
WDTest allows you to:
- Run the script in secure mode.
- Run the script several times in a row.
- Modify the time it takes to run an event, a set of events or the entire test script.
- Specify a time-out between each operation performed on the test script.
Caution: The initial action can be modified if one of the above-mentioned options is used. For example, a double click performed more slowly will be interpreted as two successive clicks (depending on the mouse properties).
Running a script in secure mode
If "Secure mode" is selected, WDTest automatically stops the execution of the script when an action (other than moving the mouse or pressing a key) is performed on a window other than the one used to record the script.
For example, if the script is run on a window other than the source one and if a mouse click triggers an unexpected action of application, the test will be stopped automatically.
Running a script several times in a row
To run the script several times in a row, specify the requested number of times in "Repetition".
Modifying the execution duration
To modify the execution duration, specify a time-out coefficient in "Coefficient":
- To increase the runtime duration: enter a value greater than 1.
- To reduce the execution duration: enter a value included between 0 and 1.
- To keep the initial execution duration: enter 1.
Specifying a time-out between each operation
To specify a time-out between each operation performed on the test script, specify this time-out (in milliseconds) in "Additional time-out".
Checking the execution of test script
Once the script has been played in continuous mode, WDTest compares the test script file (".TXT" file) and the result script file (".LOG" file). This comparison is performed only on the title of window used in an operation other than a mouse movement or a key release.
If the window title is:
- Identical: "Successful" is displayed in front of the script.
- Different: "To be checked" is displayed in front of the script.
Advanced checks: To check whether the script was successfully run:
- Display the test script and the result script in Notepad.
- Compare the content of theses scripts visually or by programming.
Playing a test script in continuous mode
To play the test script in continuous mode:
- Open or start the application to test.
- In WDTest, check the box corresponding to the test scripts to play.
Remark: The application to test must be the active application behind WDTest. When minimizing WDTest, the application to test must be the first application displayed.
- If necessary, define the execution parameters of the test script (repeat, timeout, delay, see the "Execution Parameters" paragraphe for more details).
- Click the "Play the scripts" button. The test scripts are played. The result of the comparison between the generated file and the source file is displayed in front of the script.
Remark: To stop the script execution, press Ctrl + Esc simultaneously.
Playing a test script step by step
This page is also available for…
Click [Add] to post a comment