You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issues found and fixed in #5 showed that passing arguments to commands isn't trivial, and especially may behave differently between OSs.
We should add some test coverage (at least in the integration tests, but maybe also unit tests?) to make sure that running commands with arguments does work, esp. the non-trivial cases (such as arguments containing spaces, containing quotes, containing backslashes).
The text was updated successfully, but these errors were encountered:
These test should generally try covering all public functions provided by devcmd.
For example, when adding the execToString and execInTty functions, there was a bug that the methods in ProcessExecutor weren't properly bound, which wasn't caught by the existing tests at the time. (See c24b4f8 )
The issues found and fixed in #5 showed that passing arguments to commands isn't trivial, and especially may behave differently between OSs.
We should add some test coverage (at least in the integration tests, but maybe also unit tests?) to make sure that running commands with arguments does work, esp. the non-trivial cases (such as arguments containing spaces, containing quotes, containing backslashes).
The text was updated successfully, but these errors were encountered: