[EarlGrey 2.0] Make EarlGrey cloud testing platform friendly

[joolurik]

[Based on the thread #447 ]

EarlGrey2.0 needs build product directory, sign certificates(Uploading original sign certificates to cloud system is not possible as it introduces the security risk.) and special packaging instructions to run automation in the cloud testing platform(Device Farm). These complex/un-secure steps are making almost impossible to run EarlGrey2.0 based automation in cloud CI platform.

Is there any other instructions available to make cloud testing platform integration easy? if not any plans made for the same(I can help make things faster by source contribution)?

[tirodkar]

Do you have an example setup doc for what steps EG is failing with and what precise variables / setup we have to do? You should be able to re-sign using the Xcode projects provided.

[joolurik]

I am following setup from here #447 (comment)
4th step in the steps mentioned here (#447 (comment)) needs *.p12 files.

For the 4th step, I cannot use random sign certificate/provision file because the bundle identifier of the application and sign certificate/provision file bundle identifier should match. on the other hand, i cannot upload .p12 to cloud as it introduces a security risk.

For your question, You should be able to re-sign using the Xcode projects provided?
Answer: In the cloud testing platform(e.g device-farm) only allows to upload the artifacts. it is not possible to upload entire xcode project.

Also, two more question,

1. Did you/your team run the earlgrey2.0 based automation in the cloud? if yes, which cloud platform and can you share the instructions?
2. Will it be possible to run earlgrey2.0 based automation same as XCUItest automation(We just need xctest and app files).