Skip to main content

Ready to market your stellar app?

Samsung Developer Program is your gateway to app monetization success.

Learn More

Samsung Developer Program

Using AAT to Improve Your Android App Development

Procedures to initiate AAT testing,  and review and manage AAT test results

 

AAT Testing Overview

After meeting AAT test requirements, you can submit your app for 1 or more of the AAT functional tests. 

All AAT tests are fully automated, and typically take less than 30 minutes to complete.

After AAT testing is complete:

  • You will be notified via an email that contains a link to download the test results zip file.
  • Your AAT test ticket status changes to pending.
  • At any time (Even after you close the AAT ticket.), in the comments section of the SDP Ticket Details webpage, you can copy the test results URL, and download the test results zip file via any browser.
  • At any time, you can review your AAT test requests and test results:
    • You MUST UNZIP the test results file locally.  
      CAUTION:  Do NOT open the summary.xml file from within an unzipped test results zip file.
    • Navigate the unzipped file folder structure and open the summary.xml file ONLY in an Internet Explorer browser.
      If you have any questions, you can always reach out to support@samsungdevelopers.com
    • In the summary file, you can follow links to review all requested AAT test results and their log and attachment files.
       
  • In your AAT ticket, you can post and see reply comments from AAT engineers.

 

You can close an AAT ticket, still review test results.  You can also re-open tickets and communicate with AAT engineers.

 

 

AAT Test Purposes and Test Results

NOTE:  If testing is interrupted, a test module may or may not provide partial results.

Application Manager Test

  • Verify that your app can be successfully installed on the test device and log installation events.
  • Verify that your app can be successfully uninstalled from the test device.
  • Report whether installation was successful; and if so, whether or not uninstallation was successful.
  • Provide a log of installation events (specific to test device)

IAP Test

  • Determine whether or not IAP billing permission string(s) for the Galaxy Apps and/or Google Play app stores are specified in your app manifest; and if specified, whether or not they are valid.
  • For each valid string, determine whether or not your app integrated IAP functionality for the associated app store.
  • Report whether the sale of IAP items is supported by 1 or both app store versions of your app.

Manifest Test

  • Determine the features specified in your app's manifest.
  • Verify whether or not each specified feature is supported by the test device.
  • Report the number of features specified and the number supported.
  • Provide an attachment with device, app, and feature data.

Memory Consumption Test

  • Measure heap memory usage during tested app activities and idle modes.
  • Measure suspected memory leakage after garbage collection.
  • Determine and log heap size, heap allocation, heap free, and total suspected memory leakage for tested app activities and logged memory events.
  • Determine and log total suspected memory leakage.
  • Report whether or not memory usage and suspected leakage was measured.
  • Provide memory usage data via graphs and data.
  • Provide suspected leakage data via Eclipse Memory Analyzer (MAT) (http://www.eclipse.org/mat/)

Merchandizing Requirements Test

  • Determine whether or not your free or paid app is available and can be downloaded to the test device from Galaxy Apps.
  • Determine whether or not your free or paid app is available from Google Play, and if your free app can be downloaded to the test device.
  • When your app is available in both app stores, determine whether or not your app's version codes and signature keys are the same in both app stores.
  • Report app store availability, and code and key comparisons.
  • Provide an attachment with device, app, and comparison data.

Monkey Test

  • Subject your app to randomly selected input events from 5 different types of unit tests. 
  • Monitor and log input and resulting events. 
  • If your app crashes or does not respond to 1 unit test, your app fails. 
  • If your app passes responds and continues operation after 1000 unit tests, your app passes.
  • Report whether your app passed or failed.
  • Provide a log of input and response events.

Power Consumption Test

  • Monitor and measure test device battery power usage during the test, which covers tested app activities and idle modes.
  • Report whether or not power usage was measured.
  • Provide an attached graph of minimum and average current (amps) over the duration of the test (milliseconds).  

 

NOTE: Currently, this test module can be run for the following test devices:

  • Samsung Galaxy S7 edge, model SM-G935T, OS v6.0
  • Samsung Galaxy Note 4, model SM-N910P, OS v6.0.1

 


 

 

  • Was this article helpful?