- What is the BlackBerry Dynamics SDK?
- Requirements and support for platform-specific features
- Steps to get started with the BlackBerry Dynamics SDK
- Integrating optional features
- Enforcing local compliance actions
- Adding custom policies for your app to the UEM management console
- Add a watermark to the screens in a BlackBerry Dynamics app
- Using the BBWebView library
- Using the OkHttp HTTP framework
- Prompt the user to update a BlackBerry Dynamics app
- Adding a custom logo and colors with the branding API
- Support for Night Mode
- Using zero sign-on for SaaS services through BlackBerry Enterprise Identity
- Integrating BlackBerry Enterprise Mobility Server services
- Integrating BlackBerry Analytics
- Implementing Play Integrity attestation for BlackBerry Dynamics apps
- Sample apps
- Testing and troubleshooting
- Implementing automated testing for BlackBerry Dynamics apps
- Automated testing with the BlackBerry Dynamics sample apps
- Preparing for automated testing
- Components of a sample automated testing configuration
- Execute all tests from the command line with Gradle
- Execute specific tests from the command line with Gradle
- Execute tests from the Android Studio IDE
- Add automated testing to your BlackBerry Dynamics Android app
- Configure compliance settings so you can debug your app
- Emulators and the rooted OS compliance setting
- Using enterprise simulation mode
- Troubleshooting common issues
- Logging and diagnostics
- Implementing automated testing for BlackBerry Dynamics apps
- Deploying your BlackBerry Dynamics app
- Deploying certificates to BlackBerry Dynamics apps
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 11.2
- BlackBerry Dynamics SDK for Android Development Guide
- Testing and troubleshooting
- Implementing automated testing for BlackBerry Dynamics apps
- Execute specific tests from the command line with Gradle
Execute specific tests from the command line with Gradle
Gradle
Follow these instructions to build the application, resolve dependencies, run the tests in the specified class on a connected
Android
device, and record the results.- Change the directory to samples/<app_name>.
- Run the following command:./gradlew connectedAppTestDebugAndroidTest -Pandroid.testInstrumentationRunnerArguments.class=<className>Replace<classname>with the name of your class.
You can also run a specific test manually using the following method:
- UseGradleto build theandroidTesttarget.
- Use theAndroidDebug Bridge (ADB) tool to install the app from the resulting .apk file. You can choose to uninstall any existing app first or to install as an upgrade.
- Execute specific test suites or individual tests using the ADB tool, with a command such as:adb shell am instrument -w -e debug false -e class <packageName>.<className> <packageName>.test/testRunnerReplace<packagename>and<classname>with values for your app and class.
Test results are written to the following sub-directory:
<app_name>
/build/reports/androidTests/connected/flavors/APPTEST.You can save test results using a continuous integration system. You can also use a JUnit plug-in to display the test results in a readable form, to send email messages to project members, or to take other common continuous integration actions.
For more information about running tests using the command line, see Android Studio: Test from the command line.