This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
1 / 7
Nov 2018

I have a windows machine that I’m using for testing (Xamarin Droid and WPF, i’ll ). I have Selenium running as a server when the machine restarts but I can’t figure out how to get appium to start when the server restarts. Everything works fine if I start appium (say via the desktop app) manually.

I’m probably missing an important idea and doing things the wrong way.

Our tests are in C# and we are using Teamcity and Octopus for building and deployment.

  • created

    Nov '18
  • last reply

    Nov '18
  • 6

    replies

  • 248

    views

  • 2

    users

  • 3

    links

@Aleksei

Ok. So i installed NSSM and I added Appium as a service with C:\Users\user\AppData\Roaming\npm\appium.cmd and --log C:\Testing\log\appium.log --log-teimstamp --log-level error:debug --log-no-colors for the args. I have it logging in with the local system account and checked the “allow to interact with desktop” and have tried both normal and high priority and have tried with checked and unchecked console.

In every case, the service says its running but http://localhost:4723/wd/hub/status gives no response (and there is no appium.log file).

Any thoughts? Should I call node with the main.js file directly?

@adam.vandenhoven what happen when you start in command prompt:

C:\Users\user\AppData\Roaming\npm\appium.cmd and --log C:\Testing\log\appium.log --log-teimstamp --log-level error:debug --log-no-colors

does appium starting?

I have following errors:

  1. Unrecognized arguments: andlog-teimstamp.
  2. also pls make sure that path to log file exists

@Aleksei

I’m spinning in more circles.

Appium is working and starting up when I restart but its not starting my WPF app when I run a test.

I’ve updated appium to 1.9.1 and WinAppDriver to 1.1, but it cannot start the app. The logs includes: {"status":13,"value":{"error":"unknown error","message":"Failed to locate opened application window with appId: C:\\Testing\\SystemUnderTest\\Latest\\WPF\\TestAutomation\\example.exe, and processId: 8900"}}

I also have the latest desktop app and when I run that my WPF app will start. Those logs use the same escaped path for the app so that’s not it. I’m thinking its a problem with the fact that its running from a servce?

Never worked with windows app and Appium. Sorry can not help.