1. A test robot (WDAutomate.exe) that operates with its own framework allows you to run the requested executable.
2. The executable to test must be used in the same conditions as the ones experienced by the end users (including, if necessary, the access to the databases used or to an equivalent test database, the framework used, ...).
3. To run the different tests, the executable whose test must be run loads a specific library containing the tests.
4. The tests are run and the result is saved in the Control Centers. The result can be displayed:
   • from the test robot (by selecting the executable and the test library).
   • from WINDEV (for the project version used to create the executable).

1. Create the executable: expand in the quick access buttons and select "Generate the Windows executable (32 bits)" for example.
2. Generate test library: on the "Automated tests" tab, in the "Automated test" group, click "Generate library". The test library has the following format: TEST_<ProjectName>.WDL. This library is created in the "Data of automated tests" subdirectory of the project.
3. Run the tests on the executable: on the "Automated tests" tab, in the "Automated test" group, click "Start the automated test". In this window, you must select:
   • The relevant product (WINDEV).
   • The executable whose test must be run.
   • The test library to use.
   • The command line (if necessary).
   • The tests to run.
     Remark: If the executable contains internal components, the automated tests of these internal components also appear in the list of tests that can be executed.
4. Click the "Run the tests" button. The tests are automatically run and the result is displayed in the test robot.

• Files required to start the test robot:
  • WDAutomate.exe
  • WDOutil.wdk
  • wd280xx.dll
  • wd280test.dll
• Files required to save the results of tests: Data files of Control Centers. At least one Control Center must be installed on the computer.
  The data files of Control Centers must be the ones used on the development computer (to be able to see the result of the tests). Several cases may occur:
  • if the Control Centers use a Client/Server database, the data of the Control centers is shared between the computers.
  • if the Control Centers use a HFSQL Classic database in network, the data of Control Centers is found in a shared directory.
• Executable to test with its framework (and the accesses required for the test).
• Test library and test data (the "Data of automated tests" subdirectory of the project must be copied to the computer)

Caution

Command line

• Syntax 1: Passing the executable and the test library directly:
  
  WDAutomate [EXE=<Name and path of the executable to be tested>]
  [/WDL=<Name and path of the automated test library>]
• Syntax 2: Using a script file:
  
  WDAutomate [/SCRIPT=<Script file path>]
  In this case, <Script file path> corresponds to a text file in XML format with the following content:
  
  <?xml version="1.0"?>
  <EnsembleTest>
   <EXE>Name and path of the executable to test</EXE>
   <LC>Command line to pass to the executable</LC>
   <WDL>Name and path of the automated test library</WDL>
  </EnsembleTest>
  
  In this case, the result of the scripts will be in a <Results> tag in the script file.

• "Enable the code of automatic test for the project".
• "Disable the code of automatic test for the project".