Open alexjupton opened 4 years ago
I will note that the application I'm testing uses Process.Start to run git, and it appears that it does indeed create a Git for Windows child process, but it never completes. I have it set to redirect standard output and errors from the git process to a log file, but nothing is ever written, making it appear as if it never even gets a chance to run.
If your test framework is nodejs, you may use ShellJS or node-powershell.
I don't know if your git would ask for user's input, that would be a problem if yes.
You may start with simple command like dir You may try have a full path for the git command like Process.Start C:\mytool\git.cmd
This is probably a niche case, but I am attempting to test, using selenium-appium to drive WinAppDriver, a WinForms application which performs git operations (primarily fetch and clone). The git commands work normally through the UI when the test framework is not running, but whenever I attempt to activate the commands via the test framework, the operation times out. Occasionally, the git commands complete successfully, but only after a long time (10-15 minutes). I'm unsure what could be causing the issue, but I'm fairly certain something in the selenium-appium-winappdriver cocktail is at fault.