Limitations using iPhone non-jailbroken device
1. What are the limitations of SeeTest while working on non-jail broken iPhone device comparing with Jailbroken device?
2. Do i need to keep my application in launched state to record script or I can launch application using SeeTest? (For non-jail broken iPhone device)
With SeeTest, you can test applications running on real devices, such as iPhone, iPad and iPod. SeeTest provides two options for testing iOS devices:
Full control – enables you to control any application or aspect of the device under test including 'settings' and applications that were not developed by you. This integration requires an iOS device that is jail-broken.
Application control – enables to control your application only. This integration doesn't require jail-broken device. For this option please refer to the iOS (Non-Jailbroken) section of the SeeTest manual
when using the Application control (Non-JailBroken), the application should be launched. (you cannot launch the application using SeeTest)
what about now?
There have been lots of improvements in the iOS front.
Now you don't need or want to jail-break an iOS device in order to perform actions on it or to automate the applications in it.
Without Jail-breaking a device, you can automate the instrumented application that you have installed as well as the Settings, AppStore and other applications which comes by default on the device or any other non-instrumented applications.
You can see the different options available when connecting an iOS device in the link attached below:
Its asking me the profile while launching iOS device what kid of profile it is looking for?
In order for you to be able to have full control over the iOS device you are using - you will need to use a Provisioning Profile or a .def file.
You are able to get a .def file for free from denabled.com after submitting the request with the UDID of the iOS device.
You can read more about it in the attached link: