How to Test Appdome Secured Android Apps Using Perfecto
This Knowledge Base article provides instructions on how to test Appdome-Secured Android Apps using the Perfecto Live Testing suite, a versatile testing platform for web and mobile applications. Appdome seamlessly integrates with top mobile testing solutions, enabling customers to enhance mobile app security within their existing application lifecycle with the speed and agility of DevSecOps.
Use Appdome’s Build2Test service (Recommended)
Customers with an Appdome SRM license can use Appdome’s Build2Test service to quickly and easily test their Appdome-secured mobile apps using Perfecto without the need for different Fusion Sets. With Appdome’s Build2Test service, Appdome’s in-app defense model recognizes the unique signature of these testing services and allows for easy testing without issuing a security alert or forcing the app to exit, even if these services use tools such as Magisk or Frida.
For details, see How to Use Appdome Mobile App Automation Testing.
General Information About Testing in Android Apps
Appdome protection features that may be triggered:
| Appdome feature | Reason | Behavior with Build2Test |
| Detect Developer Options | Perfecto might enable developer options to facilitate testing, which is detected as a potential security risk. | The app will detect this but will not crash, allowing testing to continue. |
| Block Android Debug Bridge (ADB) | Perfecto uses ADB for interactions during tests, which this feature blocks to prevent unauthorized control. | The app will detect ADB usage but will not crash, ensuring smooth testing. |
| Prevent App Screen Sharing | Perfecto records the screen during tests, triggering the screen-sharing protection. | The app will recognize the screen recording but will continue running without crashing. |
| Anti-tampering (on .aab apps) | Perfecto might modify the app package, triggering the anti-tampering protection. | The app will detect the modification but remain stable and functional during the test. |
| Keylogging Prevention | Testing scripts that simulate inputs in a way that resembles keylogging might trigger this feature. | The app will detect potential keylogging behavior but will not crash. |
| Detect Unlocked Bootloader | Perfecto’s devices might have unlocked bootloaders, which are detected as a security risk. | The app will acknowledge the unlocked bootloader but will continue operating normally during testing. |
| Anti Remote Desktop Control | Perfecto might use remote control tools during tests to trigger this protection. | The app will detect remote control attempts but will not terminate the session, allowing testing to proceed. |
Upload the App to the Perfecto Repository
1. Log into your Perfecto cloud at <your-cloud>. app.perfectomobile.com
2. Click on “Account Setup”.
3. Choose “Repository” from the top bar.
4. Click the upload button located at the bottom-right corner.
5. Choose and upload your app.
6. Select and define additional data (e.g., private/public repository, name, tags) and then upload the app.
Live App Testing
1. Switch to the “Manual Testing” tab in the top bar.
2. Select a device and click “OPEN”.
3. Once the device is initialized, click on the application’s icon and then “INSTALL NEW.”
4. Choose your app from the repository folder.
5. Click Next
5. Configure additional settings.
6. Click Install App. Once installed, you can use the app and test it.
NOTE
In case of any issues with the app, please send the device logs to Appdome Support by following these steps:
1. End the test and mark your results to save them.
2. Enter the link of your report.
![Perfecto[android] Release Device](https://www.appdome.com/wp-content/uploads/2023/10/perfectoandroid-release-device.png)
3. Look for the export button at the top right of the screen. Clicking it will open a dropdown menu from which you can download the device logs.
Automating App Testing on Android
For further details, see the Capabilities Builder – Appium webpage.
Troubleshooting Tips
Issue: App Fails to Run on Testing Device
Symptom: The Appdome-secured application fails to launch or crashes when running automated tests.
Possible Cause: Most automation test tools can typically be used in one of two modes: Emulator Mode and Real Device Mode (specific terms may vary according to the testing tool). If you use the automation test tool in “Emulator Mode” instead of “Real Device Mode,” the Appdome-secured application will not run on the device.
Solution:
- Ensure that the automation test tool is set to Real Device Mode. Appdome’s ONEShield feature prevents the app from running on emulators or simulators.
- Verify that the testing environment is using an actual device, not an emulator.
Issue: App Exits Unexpectedly or Displays Security Violation Message
- Symptom: The app closes unexpectedly or shows an error message stating, “Application has violated security policies, and it will be shut down.”
- Possible Causes:
- The app detects the presence of conditions it is protected against, such as running in an emulator, tampering, reverse engineering, or root detection.
- The testing tool might be running in Emulator Mode instead of Real Device Mode.
- Solution:
- Switch the testing tool to Real Device Mode or Manual Mode to prevent the app from detecting an insecure environment.
Related Articles:
- How to Test Secured Android Apps on Lambdatest
- How to Test Secured iOS Apps on Lambdatest
- How to Use Appdome’s Build2Test Service
- Test Appdome-secured Android Apps by Using SauceLabs
- Testing Secured iOS Apps by Using SauceLabs
- How to Test Secured Android Apps on BitBar
- How to Test Secured Android Apps on Browserstack
How Do I Learn More?
If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.
Thank you!
Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.
