I've spent the week trying to get Windows phone working and I'm nearly there, but it's proving to be even more roundabout than our iOS implementation.
1. Microsoft's test automation API's cost money
They require Visual Studio Premium edition which is very expensive. We could integrate this with Appium, but it would require that users have the Premium or Ultimate editions of VS2013.
2. The Windows Phone Sandbox is Hard to Penetrate
We cannot run shell commands from the automation framework as we could with iOS. The only viable entry point I have found is through the file system. I haven't confirmed this yet, but it appears you can drop files onto the device from a Windows desktop program that you can then read with the application through the mobile APIs.
3. It Will Likely Require 2-3 Servers to Get all the Work Done
The Coded UI test stuff runs on the device, which means we will likely need to start a server on the device that reads file that another server drops on the device.T hat other server will have to be in C# and then will likely need to get commands from the regular node appium server. I have not found a way to call HTTP requests from Coded UI as there's no way to give it web permissions in the app manifest (which it will throw exceptions over repeatedly) since there is no App manifest for Coded UI tests.
created
Feb '15
last reply
Aug '17
- 6
replies
- 11.1k
views
- 4
users
- 8
likes
- 6
links