- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- BlackBerry Dynamics software versions
- Requirements
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Supported launchModes
- Compatibility with the BlackBerry Dynamics Launcher Library
- Supported CPU architectures
- Supported and unsupported Android and third-party features
- FIPS-linking on Android: automatic
- Restricted key prefix
- Steps to get started with the BlackBerry Dynamics SDK
- Installing the BlackBerry Dynamics SDK for Android
- Integrating the BlackBerry Dynamics SDK in .aar format
- Using the branding API to add a custom logo and colors
- Info: Add Samsung Pass to your BlackBerry Dynamics app
- Info: APIs for secure clipboard management
- Info: Preventing autobackup to Google Drive
- Info: APIs for network status
- BlackBerry Dynamics SDK for Android: Wearable Framework
- Implementing SafetyNet attestation for BlackBerry Dynamics apps
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- 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
- Disable compliance settings that check for a compromised OS
- Emulators and the rooted OS compliance policy
- Using enterprise simulation mode
- Logging and diagnostics
- Implementing automated testing for BlackBerry Dynamics apps
- Readying your app for deployment: server setup
- Details of support for client certificates
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 5.0
- 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.