Testing Submissions: Preparing your submission for Android or iOS emulators

Introduction

The Tech to Protect Challenge includes ten unique technical contests. To help participants demonstrate their best work to the reviewers and judges – participants should ensure their applications submitted are compliant with an existing emulator for Android or iOS.
Use of this emulator will assist participants in their demos and presentations at the in-person regional codeathons and is the platform that judges will use in the online contest.
Here are a few tips and recommendations for participants to ensure their submission is complete and ready for the Judges to evaluate:
  • Each participant entry must be pre-packaged and delivered in virtual instance. Additional software or databases will not be installed for testing.
  • Participant entries should be as self-contained as possible. Participant entries can rely on a connection to the internet via a secure WiFi connection. As a security measure, this connection can only be used to access U.S. based IP addresses.
For participants using the emulator before you make your final submission, ensure that what you see is what the Judges will see – we recommend using these tools to ensure the submission you create matches your vision.


Install Android Studio

Setting up Android Studio takes just a few clicks.

Create an AVD

To create a new AVD:
  1. Open the AVD Manager by clicking Tools > AVD Manager


  1. Click Create Virtual Device, at the bottom of the AVD Manager dialog.
The Select Hardware page appears.
Notice that only some hardware profiles are indicated to include Play Store. This indicates that these profiles are fully CTS compliant and may use system images that include the Play Store app.

  1. Select a hardware profile, and then click Next.
If you don't see the hardware profile you want, you can create or import a hardware profile.
The System Image page appears.

  1. Select the system image for a particular API level, and then click Next.
The Recommended tab lists recommended system images. The other tabs include a more complete list. The right pane describes the selected system image. x86 images run the fastest in the emulator.
If you see Download next to the system image, you need to click it to download the system image. You must be connected to the internet to download it.
The API level of the target device is important, because your app won't be able to run on a system image with an API level that's less than that required by your app, as specified in the minSdkVersion attribute of the app manifest file. For more information about the relationship between system API level and minSdkVersion, see Versioning Your Apps.
If your app declares a <uses-library> element in the manifest file, the app requires a system image in which that external library is present. If you want to run your app on an emulator, create an AVD that includes the required library. To do so, you might need to use an add-on component for the AVD platform; for example, the Google APIs add-on contains the Google Maps library.
The Verify Configuration page appears.

  1. Change AVD properties as needed, and then click Finish.
Click Show Advanced Settings to show more settings, such as the skin.
The new AVD appears in the Your Virtual Devices page or the Select Deployment Target dialog.


To create an AVD starting with a copy:

  1. From the Your Virtual Devices page of the AVD Manager, right-click an AVD and select Duplicate.

Or click Menu ↓  and select Duplicate.
The Verify Configuration page appears.