Hey guys,
In this post I’m going to show you how to configure the MonkeyTalk iOS agent in XCode. Let’s jump right to it.
First, you’ll need to install the Monkeytalk IDE. To do that just follow the steps below.
Once you’ve installed MonkeyTalk, you’ll need to install the iOS Agent. Follow the steps below to do that.
After you’ve installed the iOS Agent, you’ll need to configure the libraries and build settings. To do that
When you do that, you’ll notice that the Log output shows that MonkeyTalk has successfully loaded in your app (as depicted in the screenshot below).
Now let’s create a test project for iOS which we can record using MonkeyTalk. Follow the steps below to do that.
Now let’s test our sample project on the iOS simulator. To do that you’ll need to have your MonkeyTalk enabled app running on your Simulator. Once you’ve got the app running:
To connect your iOS device with the MonkeyTalk IDE use following steps:
Please note that for this to work, both the IDE and your mobile device should be on same network.
To record the app’s UI interactions through the MonkeyTalk IDE, follow the steps below.
Note: If the buttons are disabled it means that your device/simulator is not connected with the IDE.
All the results from the execution of test will display in the console. You’ll notice that displays the status and result of each testing command executed. These commands are shown in three different formats
The scripts used are editable after recording. You can even write these scripts without recording if you like. You can also view the screen shots for every command executed, these are saved under the screenshots folder (as depicted below).
Since MonkeyTalk records each user interface action as a Command, every MonkeyTalk Command has the same simple format:“Component MonkeyId Action Arguments”
In this command, the Component is stands for the UI component used, for example a Button or Input field. These components are platform-independent by the way.
The MonkeyId identifies which Component is being specified. For example, the OK button or the Cancel button. An asterisk (*) is used as a wildcard to match the first component found of the specified component type.
The Action referred to in the command is the UI interaction being recorded, for example, Tap or EnterText. The Arguments being referred to are additional values that are needed to describe the action.
Monkey talk gives a unique MonkeyID to every component during its execution. This ID is usually based on the accessibility variable each component has. If a particular component doesn’t have an accessibility variable assigned, then MonkeyTalk assigns a random ID to it during recording. This ID will depend on the position of the UI component.
The problem with this MonkeyTalk defined ID is that the next time when the test is executed, this ID will not be found by MonkeyTalk since it was randomly generated at the time of recording. To solve this issue you’ll need to assign labels to all the components. You can add these accessibility variables by following the steps below:
And that’s it. Hope you guys find this post useful.
As a leading mobile app development company (iPhone, Android, Windows Phone, HTML5 app development), Folio3 specializes in native app development services and cross platform mobile app development services for the iPhone and iPad. We also offer extensive mobile app testing and QA services. If you have a mobile app idea that you’d like to discuss please or would like to know more about our iPhone app development services, please Contact Us. Learn more about our iPhone, Android and Windows Phone app development services.
USA408 365 4638
1301 Shoreway Road, Suite 160,
Belmont, CA 94002
Whether you are a large enterprise looking to augment your teams with experts resources or an SME looking to scale your business or a startup looking to build something.
We are your digital growth partner.
Tel:
+1 408 365 4638
Support:
+1 (408) 512 1812
COMMENTS ()
Tweet