Creating and recording the scenario

• in the application directly, by programming, with dbgStartRecording. Several WLanguage functions are available:
  

  dbgStartRecording	Starts recording the scenario.
  dbgEndRecording	Stops recording the scenario

• without modifying the application, via a specific file. To do so, create a file named <Executable Name>.WX beside the executable of the application.
  This file must contain the following lines:
  
  [Scenario]
  Enabled = <0/1>
  File = <Name of WSCT file>
  DLLPath = <DLL path for test>
  
  Let's take a look at these lines:
  • Enabled: This parameter must correspond to 0 to avoid recording the scenario and to 1 to record the scenario
  • File: Name of the scenario file ("wsct" extension). This name can be built from the following elements:
    

    [%ExeDir%]	Directory of executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.
    [%ExeName%]	Executable name.
    [%Date%]	Start date of scenario file.
    [%Time%]	Start time of scenario file.
    [%UserName%]	Name of current user.
    [%ComputerName%]	Computer name.
    Versions 18 and later [%DataDir%] New in version 18 [%DataDir%] [%DataDir%]	Directory of HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir.
    Versions 18 and later [%DirUserData%] New in version 18 [%DirUserData%] [%DirUserData%]	Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser.

  • CheminDLL: path used to access the wdxxxtest.dll library. This DLL is required to create the scenario.

1. Open the requested project in WINDEV.
2. Under the "Automatic tests" tab, in the "Tests" group, scroll down "New" and select "Import a scenario recorded on the application".
3. Select the scenario file to import (wsct extension).
4. The scenario is automatically imported into the project:
   • An automatic test is created for each window used in the scenario. If some tests already exist for the window, the imported tests are automatically created in the test associated with the window.
   • The imported tests are automatically in construction: the developer must check the tests and enable them if necessary.
   • The description windows corresponding to the imported tests are displayed in the editor: the tests can be viewed one by one.