ToolsLauncher did not generate report folder if the fsReportPath{i} is a relative path

[soleverxu]

Tool FTToolsLauncher

Describe the bug When specifying the explicit report path for a test via the parameter fsReportPath{i} and that report path is a relative path, for example, fsReportPath1=MyReport1, the specified report directory is not created in the current working directory (if the specified does not exist).

To Reproduce Steps to reproduce the behavior:

1. Prepare a parameter file with one test Test1=xxx and fsReportPath1=MyReport1
2. Ensure the MyReport1 folder does not exist in the current working directory
3. Run the FTToolsLauncher with the above parameter file
4. Check if the MyReport1 folder is created in the current working directory

Expected behavior The explicit report folder shall be created and report shall be generated there, if given a relative path.

OS and testing tools (please complete the following information):

• OS: Windows 10
• UFT One version: 15.0.2

[soleverxu]

Fixed in the release v1.0 beta (rev.8)