Fix CLI path handling in tests #33
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Fixed CLI test execution by properly quoting the CLI path.
What changed?
Added double quotes around the CLI path in the
runCliWithParametersfunction to ensure proper handling of paths with spaces.How to test?
Why make this change?
Paths often contain spaces and special characters that can cause issues when not properly quoted in command execution. This fix ensures that the CLI tests run reliably across all operating systems, by properly escaping the path to the CLI executable.