Starts recording a test scenario (also called reproduction scenario).
The reproduction scenario is a ".wsct" file containing the test scenario.
This file can be supplied to the application designer. To include this scenario in the automated tests of the application, go to the "Automated tests" tab, "Tests" group, expand "New" and select "Import a scenario recorded on the application".
<Result> = dbgStartRecording([<Name of scenario file>])
- True if the recording was started,
- False otherwise.
<Name of scenario file>: Optional character string
Location and name of the scenario file to create. The name and location of the file can be:
- fully customized.
- built using the following keywords:
|[%ExeDir%]||Directory of the executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.|
|[%Date%]||Start date of scenario (YYYYMMDD format).|
|[%Time%]||Start time of scenario (HHMMSS format).|
|[%UserName%]||Name of the current user.|
|[%DataDir%]||Directory of the HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir.|
|[%DirUserData%]||Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser.|
By default, the name of the scenario file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
For example: "C:\Users\Doc\AppData\Roaming\WINDEV Applications\MyApp\Myapp_20161023_130812.wsct".
Caution: If you use the dynamic string construction ("Allow "[% %]" in the strings" in the "Compilation" tab of the project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
- dbgStartRecording has no effect if a scenario is already being recorded.
- dbgEndRecording is used to end the recording of the scenario.
- The recording of the scenario can also be started via the ".wx" file found beside the executable. For more details, see Scenario created by the user.