As we all know a fact that goes along with logging out process, the way to find out and reconstruct causes is essential when bugs are detected by Testers.
However, a tester cannot ensure all the time that they could remember all steps that cause that bug or error. Some still remember but some may ignore the intensity level of bugs then forget to provide to the Development department to check and fix.
In order to solve this issue, we’re using Monkey Talk tool for the main purposes of testing and debug. It’s totally FREE with open source and really friendly to users by its usability. About the utilities as well as its instruction for use, there’re many documents mentioned about it.
In this article, I just share my experience in a field of conducting a test for iOS apps in Windows operation system.
- Don’t miss: How much does it cost to make an App: Our 2019 Industry Research
As you could see, when deploying almost all app, developers use Mac OS & Xcode meanwhile testers use Windows OS. This leads to many problems and unfavourable things; for example, in order to get log files on Mac OS, it’s very convenient that you just only need Xcode while it’s a little bit complicated on Windows OS.
Based on my experience, currently many teams have used this tool (or another one) and they show that it would be more effective when testing on Mac OS.
When you build any apps on any devices, Windows does not have permission to access deep inside and it’s hard to see how users may interact with the system.
Therefore, MonkeyTalk serves you an “agent” – a neutral environment to interact with your app and also necessary tools installed on Windows are provided. We could imagine this agent is like a shell which may wrap the app and we can take all the information inside.
Table of Contents
Testing iOS Apps with Monkey Talk: Step-by-step
Firstly, developers must take the agent of MonkeyTalk. It gives you two options to download an only agent or full version but remember to sign up first!
- (Download HERE)
At the second step, you need to duplicate app target and edit name to differentiate with the main target, then changing to related name in the Tab “Manager Scheme”.
Thirdly, adding lib libMonkeyTalk-1.x.x.a into the project, you could choose “Copy items into destination group’s folder” if you haven’t got it and IMPORTANTLY you need to add the right target test (it differs the target of the main app).
Preparing for the next step, we’ll need to set Configures of target test and then add them to appropriate lib. These libs are required to add into the Tab “Link Binary With Libraries” at Build phrases of target test: libstdc++.6.0.9.dylib, libsqlite3.dylib, CFNetwork.framework & QuartzCore.framework.
Next, set the flag “Other Linker Flags” at “Build Settings” tab to “-all_load-lstdc++”
Step 6 (Final)
After setting the flag above, we run TARGET TEST on simulator or device (cleaning step before building an app is recommended).
Those all basic steps to build Agent for MonkeyTalk, and now you could see this guiding video below to know how to test the iOS app by using this software on Windows OS.