Test reports

  • Article
  • 5 minutes to read

When your tests execute in App Center Test, we generate reports with a summary and detailed information for

  • the test run
  • the tests
  • the devices.

At the completion of the test run, y'all can view these reports in the Tests section of App Center.

Read App Center Examination Core concepts to understand the terms and concepts used below.

Starting from the App Center My Apps page, select an awarding, and then select Tests in the navigation listing. From the Exam runs dashboard all test runs in the default examination series for that awarding are displayed.

Exam runs dashboard

Note

Only the 50 almost contempo test runs volition be shown for the selected Test Serial on the Dashboard.

App Center Test, test runs page

The color green or a check mark on a green background indicates passing and the color cherry-red or a lightning bolt on a red groundwork indicates failing, throughout the test reports.

  • The Test serial push button filters or creates a test series.
  • The New examination run push starts a sorcerer that helps you to create a sample command line to submit a new test run.
  • The Number of Tests graphic near the acme left shows the test run history with the number of tests passed and tests failed. Click in this graph to navigate to a specific test run.
  • The Peak Memory graphic at top right shows exam run history for the peak memory consumed by the application. Click in this graph to navigate to a specific test run.
  • The Test runs list shows summary test run results including Engagement, Duration, Condition, Results, and number of Devices. When filtering by test series, merely examination runs from the selected test serial are shown.

Click on the examination run of interest to see the Test run summary folio for that test run.

Test run summary

App Center Test, test run summary page

Click in the Test Runs navigation listing on the left to view the summary for that examination run in the detail pane. The detail pane shows:

  • The date and time the exam run was submitted.
  • The number of Devices in the exam run.
  • The Run Time for the examination run. Run time is the total elapsed time from when the test run was submitted until the final reports are viewable in App Center Test.
  • The number of tests in the exam run.
  • The Tests passed graphic shows the pct and number of tests that passed. To pass a test, must laissez passer on every device in the test run.
  • The Devices passed graphic shows the percentage and number of devices on which all tests passed.
  • The Tests listing displays the tests in the exam run.

Click on a exam of interest in the particular pane and either the Examination overview page or the Test detail folio opens, depending on the number of devices in the test run. If there's one device, App Center opens the Test detail folio and if there are multiple devices, App Eye opens the Exam overview page where you tin navigate to a Test detail page for a specific device.

Test overview

App Center Test, test page

This page only displays if there are multiple devices in the test run.

The Tests navigation list on the left shows the test step proper name or exam characterization. Navigate by clicking in this list or scrolling up and downward with the 'thousand' (upwardly) or 'j' (down) keys.

The detail pane shows screenshots for each of the devices in the examination run for the selected test step. The Device and Os version are listed beneath the screenshot. The Filter icon near the height right lets you filter by diverse device attributes like class cistron, cpu, and Os version.

Click on a screenshot to navigate to the Examination particular page for that device.

Download the full sized screenshot

To speed upwardly the page rendering, all screenshots are resized to match multiple browser windows sizes. For larger screenshots, the exam written report automatically renders with the fifty% screenshot. The API can be used to download the full sized screenshots by getting the examination report https://openapi.appcenter.ms/#/test/test_getTestReport and from the report fetch the step written report (step_report_url). Within the step written report, there'll be a field called original (/deviceScreenshots/*/screenshot/urls/original) that volition point to the full size screenshot.

Follow this link for instructions on how to utilize App Center'south API

Test detail

App Center Test, test detail page

The Tests navigation list on the left shows the test step name or test label. Navigate by clicking in this list or scrolling upward and downwardly with the 'thousand' (upward) or 'j' (down) keys.

  • The test name, device and os version are listed across the top of the page.
  • The screenshot is displayed for the selected device for the selected exam footstep.
  • The Details icon displays device information similar memory, CPU speed, and dimensions.
  • Clicking the Logs icon will navigate to the Examination logs folio.
  • The Hardware usage graph displays the Memory and CPU utilization during the examination.
  • Duration shows the time to complete this test and test step. The test stride fourth dimension shown here is the test time starting with the displayed screenshot and the selected test step until the post-obit screenshot. It isn't the time ending with this screenshot.

Examination logs

App Center Test, test logs page

The tabs beyond the summit of the folio include Exam Logs and Device Logs. There may be others depending on the test framework used. A Stack Trace tab will appear if whatsoever stack traces were captured for this exam run for this device.

Test logs tab

Click the Test Logs tab near the top of the page.

Test logs and framework specific logs are the output from the examination framework and provide clues as to why a test failed or issues involving the test framework.

Stack trace tab

Click the Stack Trace tab near the top of the page.

Stack traces are errors captured during the test run. Any stack traces should exist examined forth with the test logs and device logs for more context to troubleshoot application issues.

On iOS, the stack trace is relevant to any problems with the tests. On Android, if your awarding code is included in role of the stack trace it's relevant.

Device log tab

Click the Device Logs tab well-nigh the top of the page.

The device log is the output from the device during the test run. Click Download device log to access all of the the device log file. When the log file starts loading in your web browser, you lot tin can use your spider web browser to salvage the file locally and apply local tools to examine the log. Saving the file locally will usually exist faster for multiple searches or when the device log file is large.

Getting help

You tin contact back up in the App Centre portal. In the upper right corner of screen, select the Assist (?) carte du jour, so choose 'Contact support'. Our dedicated support team will respond to your questions.

If you want aid with a examination run, navigate to the test run in question and copy the URL from your browser and paste it into the support conversation. A test run URL looks like something like https://appcenter.ms/orgs/OrgName/apps/App-Name/exam/runs/77a1c67e-2cfb-4bbd-a75a-eb2b4fd0a747.