Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Running winappdriver in the background piped to a log file

See original GitHub issue

if I start a new powershell and execute winappdriver it is all fine, but I need it to behave more like chromedriver and geckodriver, that I can start it in the background and it logs to file. and no output in the console. No extra console open.

I tried several combinations of: & { Start-Job 'C:\Program Files (x86)\Windows Application Driver\WinAppDriver.exe' | Out-File .\winappdriver.out.txt}

Would be nice to get some info on how to set up this.

`(get-command(“C:\Program Files (x86)\Windows Application Driver\WinAppDriver.exe”)).Version

Major Minor Build Revision

1 1 1903 8001 `

Issue Analytics

State:
Created 4 years ago
Comments:7

Top GitHub Comments

2reactions

fenchucommented, Sep 10, 2019

I get this to work:

& { Start-Process -NoNewWindow 'C:\Program Files (x86)\Windows Application Driver\WinAppDriver.exe' -RedirectStandardOutput .\winappdriver.txt }

0reactions

naeemakramcommented, Oct 11, 2019

Hi, I’ve published a course about test automation using WinAppDriver. Given below is a special launch promo code(valid 4 days). Automated UI Testing Windows Apps in Appium WinAppDriver, C#