Learn how to test Appdome-secured Android & iOS Apps Using SeeTest automation test platform for DevSecOps. Appdome works with all leading mobile automation testing solutions to help customers achieve comprehensive mobile app security at DevSecOps speed and agility, all within the app’s existing application lifecycle.
Click Open to launch the selected device.
Click the Applications button on the left menu.
In the opened APP MANAGER window, select the “Device” tab, then click the “+” icon at the bottom.
a. Either Enable a Threat Event for “Detect App is Debuggable”
b. When signing the app, use a provisioning profile that includes a “debuggable” entitlement, and sign the app using Appdome’s automated app signing
After successfully building and signing your app on Appdome, go to https://cloud.seetest.io and login to your account.
Most automation test tools can typically be used in one of two modes: emulator mode and manual mode (specific terms may vary according to the testing tool). If you use the automation test tool in “emulator mode” instead of “manual mode”, the Appdome-secured application will not run on the device. This is expected because Appdome ONEShield protects apps from running on emulators/simulators. Instead, you should run the automation test tool in manual mode.
If you see a message such as: “Application has violated security policies and it will be shut down”, this means that (1) techniques such as emulators, tampering, or reverse engineering are present, and (2) the Fusion Set does not contain Appdome Threat-Events. This is expected because Appdome ONEShield protects against those conditions. You can either remove the triggering condition or use Appdome Threat Events if applicable.