On Dec 16, 2015, at 11:18 AM, rpzrpz...@gmail.com<mailto:rpzrpz...@gmail.com> 
wrote:



On 12/16/2015 10:38 AM, Edward Sutton wrote:
On Dec 16, 2015, at 8:49 AM, rpzrpz...@gmail.com<mailto:rpzrpz...@gmail.com> 
wrote:

I use Jenkins now for Android, iOS, OS X, Linux, & Windows builds. Jenkins + 
Docker sounds interesting. I assume one advantage is it is light weight 
compared to having to store a bunch of large VM images? Can Docker be used to 
deploy OS X Xcode and Windows Visual Studio build slaves? Or is the Docker 
engine always running a Linux system of some sort regardless if the engine host 
is Windows? -Ed

Edward:

How are you verifying Android and IOS builds?

Using simulators or actual devices?
Manual testing using actual hardware.

An automated-smoke test would be nice. I do not know how I would do this.

-Ed


Yes, real device testing in the CI would be great.

For android, you would have to automate GDB to uninstall and reinstall apk 
files.

Then have code to support the simulation of user input and sensor data.

It would be likely impossible to verify the GUI side, but models and business 
logic could be verified.

And high volume testing could be executed.

IOS is a different animal.  Likely have to jailbreak a device just to get into 
it for automated program removal and testing.

I have run into issues when I skipped manual build verification.  I have had 
issues with both iOS TestFlight and Android Beta testing builds that did not 
run or install properly,

Even automated smoke-test build verification using iOS simulator and Android 
simulator would be beneficial.

ADB and Android might work.

Not sure how to communicate with an iOS simulator.  I think the simulator's 
file system can read by the OS X host.

-Ed

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for any damage caused 
by any virus transmitted by this email.
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to