Using the Windows Recorder, you can create a script that simulates using a native application on a mobile device. Scripts for monitoring mobile apps leverage the API calls and HTTP requests from the mobile app. See Creating scripts for native mobile applications for detailed instructions.
When you have finished recording the script, you can upload it to the Synthetic Classic Portal and create tests for running it on designated mobile nodes.
Native application considerations
Usually, a basic native application either does not require credentials or requires only a username and password. In most cases, the credentials are stored and re-used successfully during script playback.
Some native applications are implemented with additional security. For example, a banking application returns a session token that can only be used once. After recording the script, you must insert custom code into the script that retrieves the session token so the script can run successfully.
The security implemented in some mobile native applications prevent the Recorder from recording the script. For example:
- The mobile native application cannot run on a proxy server. A proxy server is required for the Recorder to record the mobile application script on the device. If the mobile application cannot run on a proxy server, the Recorder cannot record the script.
- The mobile native application requires verification from a SIMM card while it is being used.
- The mobile native application blocks all third-party packet sniffing.
Because native applications that require higher security use many different methods to provide that security, it is not possible to provide code samples for each case. If your app security is preventing you from successfully recording a script and there is no development resource available to help you implement these changes, contact Customer Support.