Appium+WDA+Python based IOS automation testing full record (three): real machine demo running

Previous review:

Appium+WDA+Python based IOS automation test full record (two): the simulator demo run

Appium+WDA+Python based IOS automation test full record (one): the environment setup

In the simulator will be the demo run through, it is necessary to test on the real machine.

After running the demo in the simulator, you will have to test it on a real machine, and the simulator will always serve the real machine.

In the real machine is mainly involved in the signature and certificate issues, a blog written particularly well, but in fact I did not understand, RSA algorithms, such as early in the cryptography course back to the teacher.

The principle of iOS App signing

This is a simple record of how to configure certificates.

Find the Build Setting configuration section in xcode (the reason I put this image up is because I couldn't find it in the first place, and newcomers can't find anything):

Change the contents of the three fields:

Code Siging identify the developer that corresponds to the certificate

Product Bundle Identify the developer that corresponds to the product bundle that corresponds to the product bundle that corresponds to the product bundle. Product Bundle Identify the corresponding bundleID

The Provisioning Profile contains data such as certificates/entitlements and packets signed by Apple's backend private key.

The packet ends in a .mobileprovision file format. You can see the information in it by typing the following command in the terminal

After changing the profile, we can install our development on the real machine, and choose to run it on the real machine at this time.

After the test app is installed on the real machine, you have to think about how to open a py script to test it on the real machine.

Here we need to pay attention to two points:

Finally found the address is probably as follows:

Put into the xcode for signing the certificate configuration, note that although we open the WebDriverAgent folder, but we want to configure the WebdDriverAgentRunner in its Build Settings to do with the certificate. Settings for certificate-related configuration

After the configuration is complete, you also need to add a RoutingHTTPServer.frameork to the WebdDriverAgentRunner

After clicking on Add - >add Other

In the following path, you can look for The framework

must be in the appium file path!

I didn't say much about wda because I don't know much about it yet, but I'll add more knowledge when I do

The py scripts are mainly configuration changes, but the main files are at the beginning of the blog for the emulator demod

The configuration changes on the real machine are as follows:

Then you start appium and see that the real machine has the The toilet app is loaded with WebDriverAgentRunner and then the script is run in python and it's ok!

The above is a brief description of how to set up the environment - "run the demo in the emulator - "run the demo on the real machine, without going into the principles.

After that, there's still a jump in the Android environment to build

wda's inspector-related environment hasn't been documented yet~

[Tbc]

Personal blogs:

Attack of the Programming Ming

This is the first time we've seen a program like this in the past, and it was the first time we've seen one in the past.