PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Runtime parameters of a 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 the test script
  • Playing a test script in continuous mode
  • Playing a test script step by step
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
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 the test script for more details.
  • step by step. You can run:
    • the events of the script 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.
An event, a set of events or the entire script can be run according to the runtime parameters.
See Runtime parameters of a test script for more details.
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 the operations performed.
Runtime parameters of a 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 the 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 the 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 the window used in an operation other than a mouse movement or the release of a key.
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:
  1. Display the test script and the result script in Notepad.
  2. 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:
  1. Open or start the application to test.
  2. In WDTest, check the box corresponding to the test scripts to play.
    Note: The application to test must be the active application behind WDTest. When minimizing WDTest, the application to test must be the first application displayed.
  3. If necessary, define the execution parameters of the test script (repeat, timeout, delay, see the "Execution Parameters" paragraphe for more details).
  4. 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.
    Note: To stop the execution of the script, press the [Ctrl]+[Esc] keys simultaneously.
Playing a test script step by step
To play the test script step by step:
  1. Open or start the application to test.
  2. In WDTest, check the box corresponding to the test script to play.
    Notes:
    • A single script can be run step by step.
    • The application to test must be the active application behind WDTest. When minimizing WDTest, the application to test must be the first application displayed.
  3. Click the "Run step by step" button. The window for step-by-step execution is displayed. This window lists all the events found in the current test script.
  4. The window for step-by-step execution is used to perform the following operations:
    • Run the test script in continuous mode: click .
      All the events following the last event run will be run according to the specified parameters.
    • Play the test script step by step: click .
      The selected event will be run according to the specified parameters and the window for step-by-step execution will be re-displayed after its execution. The event found after the event run will be automatically selected.
    • Play the script until a specific event: select the last event to run and click .
      All the events found between the last event run and the selected event will be run according to the specified parameters. The widow for step-by-step execution will be re-displayed after the execution of events. The last event run will be automatically selected.
    • Include one or more breakpoints in the script: select the event for which a breakpoint must be inserted and click .
      During the script execution, the window for step-by-step execution will be displayed as soon as a breakpoint is reached.
Notes:
  • These breakpoints are taken into account only when a set of events or the entire script is run from the window for step-by-step execution.
  • To remove a breakpoint, select the event for which the breakpoint must be removed and click . To remove all the breakpoints, click .
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment