Mobile testcase development is essentially identical to testcase development for traditional web applications in that the goal is to record a testcase for later replay. Several things make this potentially more complicated, and the exact steps may depend on the specifics of your device:
(1) You'll need to get your (physical or emulated) mobile device to direct traffic to Load Tester's proxy. Do this by matching the proxy settings on your mobile device to the settings found in the tool under Window > Preference > Web Performance > Recording. You can launch a recording without starting any web browser, and the proxied requests from your mobile device will contribute to the recording.
(2) Your mobile device will need to trust Load Tester's root certificate. The certificate can be obtained from the Proxy Check page that comes up at the start of every recording and needs to be imported and trusted in your device's certificate store.
(3) Load Tester automatically begins each recording (in a desktop web browser) in private browsing mode so that pre-existing cache and cookies don't contribute to the testcase. In the mobile browser, you'll need to do this manually. For a mobile application, this may mean resetting the app data back to its factory state.
(4) After the testcase has been recorded, there may be extra difficulties getting it to replay correctly, due to the fact that mobile applications aren't constrained by web standards that make it easy for the tool to automatically configure most traditional web applications. As long as your support agreement with us is up-to-date, we can support you to develop appropriate detection rules.
You likely have more detailed questions about specific mobile technologies. If so, please open a ticket with us so that we can provide advice tailored to your situation.