Find your Developer Device Platform test results

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

This guide describes how to find the results of tests triggered following the Developer Device Platform Device Run guide.

Before you begin

These steps assume that you have already created a Google Cloud project, completed the setup steps in the Developer Device Platform Quickstart guide, and authenticated with gcloud in the terminal.

At the command line

See a basic summary of your test result with this command and your session ID:

gcloud beta device-run sessions describe your_session_id

Which returns results resembling:

Session [session-number] finished with result [FAILED].
Result files are stored at [https://console.cloud.google.com/storage/browser/<your_project_id>/automation/sessions/session-number/].
JOB NAME  EXECUTION NAME  EXECUTION RESULT
job-000   all             FAILED: 2 test cases failed, 5 passed
job-001   all             PASS

For each device type ID you specified with the --device flag, one job is generated in the session. The job index will follow the order of your device IDs. Test failures are expected and should be investigated and resolved through iterative improvements and runs.

Tip: To get additional details about a test session, append --full to the previously run describe command like so:

gcloud beta device-run sessions describe your_session_id --full

Which returns results resembling:

name: projects/your-project-id/locations/global/sessions/session-370961e1
sessionConfig:
  displayName: instrumentation-session
  jobConfigs:
  -   action:
      androidInstrumentationTest:
        testInstallable:
          files:
          -   gcsInputFile:
              path: gs://your-project-id-devicerun/automation/inputs/2026-07-30_11:28.31915956_8514/app_name_test.apk
    allocationConfig:
      deviceConfigs:
      -   actions:
        -   androidInstallPackages:
            installables:
            -   files:
              -   gcsInputFile:
                  path: gs://your-project-id-devicerun/automation/inputs/2026-07-30_11:28.31915956_8514/app_name.apk
        -   androidLogcat: {}
        requirement:
          deviceId: pa3q-35
    displayName: job-000
  outputDirectoryConfig:
    gcsOutputDirectory:
      path: gs://your-project-id-devicerun/automation/sessions
sessionReport:
  endTime: '2026-07-30T03:30:05.838Z'
  id: 6587313f-fdf7-418a-a9b9-b6fa98dff838
  jobReports:
  -   displayName: job-000
    endTime: '2026-07-30T03:30:04.601Z'
    executionReports:
    -   displayName: all
      endTime: '2026-07-30T03:30:02.151Z'
      id: 29b167dd-dde9-4ea9-b2cd-738049083fc9
      outputFiles:
      -   gcsOutputFile:
          path: gs://your-project-id-devicerun/automation/sessions/session-370961e1/job-000/execution-000/logcat.txt
      -   gcsOutputFile:
          path: gs://your-project-id-devicerun/automation/sessions/session-370961e1/job-000/execution-000/instrument.log
      -   gcsOutputFile:
          path: gs://your-project-id-devicerun/automation/sessions/session-370961e1/job-000/execution-000/test_result.xml
      result:
        cause:
          summary:
            message: One or more test assertions or test methods failed. Inspect the
              test runner logs and structured test results for details.
            reason: TEST_CASE_FAILURE
            type: CUSTOMER
        resultType: FAILED
      startTime: '2026-07-30T03:29:32.769Z'
      status:
        progressMessages:
        -   2 test cases failed, 5 passed
        statusType: DONE
    id: 7974e37a-2928-4aaf-abba-3a8b6bae853b
    result:
      cause:
        summary:
          message: Job has one or more failed tests. See execution reports for details.
          reason: JOB_HAS_FAILED_TESTS
      resultType: FAILED
    startTime: '2026-07-30T03:28:53.756Z'
    status:
      statusType: DONE
  result:
    cause:
      summary:
        message: Session has one or more failed jobs. See job reports for details.
        reason: SESSION_HAS_FAILED_JOBS
    resultType: FAILED
  startTime: '2026-07-30T03:28:52.702Z'
  status:
    statusType: DONE

In web browser

For full details, load the URL to the bucket containing your test results from the test output. It should resemble: https://console.cloud.google.com/storage/browser/storage/browser/<your_project_id>/automation/sessions/<session_id>

Navigating

To browse for your logs in the Google Cloud console web interface, follow these steps:

1. In a browser, append your project name as used in the gcloud config set project command to the URL https://console.cloud.google.com/?project= and load the page.
2. Expand the menu at top left.
3. Find Cloud Storage.
4. From the storage menu, select Buckets.
5. In the first column, click the name of your project.
6. Click Automation.
7. Click Sessions.
8. In the Filter field, paste the session ID from your latest test run (see the test output).
9. Click the resulting session name.
10. Select job-* to view test_result_merged.xml, which contains comprehensive result details across all test cases.
11. Open execution-* for a breakdown of each individual shard. Inside this folder, navigate to:
    • instrumentation.log
    • logcat.txt
    • test_result.xml
12. Visit the public and authenticated URLs to understand the test results.

File structure

Explore the log files in your Cloud Storage bucket to understand more about the test failure. The file structure resembles:

-   gs://my_project_id_devicerun/automation
  -   inputs/
    -   2026-05-29_10:13.026220_JZTM
      -   app.apk
      -   test.apk
  -   sessions/
    -   session-number
      -   job-000/
        -   test_results_merged.xml
        -   execution-000/
          -   instrumentation.log
          -   test_result.xml
          -   logcat.txt
          -   video.mp4
        -   execution-001/
          -   instrumentation_output.txt
          -   junit.xml
          -   logcat.txt
          -   video.mp4
      -   job-001/
    -   session-number

Understand the results

The test_result.xml or test_result_merged.xml file generated in your output is a standard JUnit XML file. This file contains the per-test-method results, allowing you to review the specific pass or fail status, execution time, and error traces for each individual test method. You can readily integrate and parse this file with most Continuous Integration and Continuous Delivery (CI/CD) systems and test reporting tools.

Supporting documentation

• Fundamentals of testing Android apps
• Build instrumented tests
• About Cloud Storage buckets

What's next

Next up, try our Developer Device Platform Device Streaming API.