Extension Version
1.4.39
OpenEdge Version
12.8
Bug Description
Executing ABLUnit tests on OpenEdge projects fails if the workspace path contains space characters (e.g., C:\projects\my test project\).
Steps to reproduce
- Create or open an OpenEdge workspace in a directory that has a space in its path name.
- Run an ABLUnit test from the VS Code Test Explorer.
- The execution fails in the terminal with shell parsing errors or truncated configuration paths:
** Unable to open parameter file C:/projects/my, errno 2. (1247)
Cause of the issue
- Command-line path parameters (such as
-pf, -T, -profile, -p, and the executable path itself) are split by the Windows shell at space characters because they are not quoted.
- The parameter string passed to
-param uses spaces to delimit individual key-value pairs (e.g., CFG=path ALIASES=...). If a path contains a space, the value is truncated during parsing on the ABL side.
Solution
See #596.
Extension Version
1.4.39
OpenEdge Version
12.8
Bug Description
Executing ABLUnit tests on OpenEdge projects fails if the workspace path contains space characters (e.g.,
C:\projects\my test project\).Steps to reproduce
Cause of the issue
-pf,-T,-profile,-p, and the executable path itself) are split by the Windows shell at space characters because they are not quoted.-paramuses spaces to delimit individual key-value pairs (e.g.,CFG=path ALIASES=...). If a path contains a space, the value is truncated during parsing on the ABL side.Solution
See #596.