Skip to main content
Cypress 10 support is here! Upgrade your BrowserStack Cypress-CLI to v1.18.0 and start testing. Try now!

View Test Results

View your Cypress test results on the Automate Dashboard.

Protip: Starting CLI v1.6.0 and higher, if you run tests in the sync mode, test results are automatically saved to the results folder as HTML and JSON files. You can attach these files to your CI runs.

Overview

After running your Cypress tests on BrowserStack, you can view the test results on the Automate dashboard.

The tests are grouped by their build names and further combined into test spec and browser combinations (OS, OS version, browser, and browser version) you selected to run your tests on. The Automate dashboard displays test results, video, and a screenshot of the error in case of a failed test.

You can view the results of the tests, as well as debug the tests using the different logs that are accessible from the dashboard.

Build view in Automate dashboard

The Automate dashboard displays a list of builds that have run through your organization’s account as shown in the following screenshot: Automate Dashboard Build View

  1. Sidebar: Enables quick access to all your builds. The sidebar also displays meta-information such as number of sessions, status of sessions, and project name.

  2. Builds filter: Filters your builds by user, project, framework or status. As you apply filters, the dashboard URL changes, enabling you to share filtered views with other team members.

  3. Global search: Searches for projects, builds, and sessions by their name or IDs.

  4. Build name: Shows the build name and project name.

  5. Build level filter: Filters the sessions in a build by spec status, OS, or Browser.

  6. Build meta: Provides useful information about the build, such as, build status, build duration, number of parallels used, build ID and the name of the user who executed the build.

  7. Duration: View a detailed breakdown of the time elapsed during the test by holding the pointer over Duration label.Build Duration These details include:
    • queue_time: Time spent in queue due to parallels not being available.
    • setup_time: Time spent in setting up the machine, such as installing the required npm packages, downloading specs, setting up local connection, etc.
    • test_run_time: Time spent in running your tests.
    • idle_time: Total time duration when one or more parallels are free while tests are still running on other terminals and the build is not yet completed.
    • misc_time: Any additional time spent in doing activities other than those listed above is calculated under miscellaneous time.
  8. Parallels and queued sessions: Displays the total number of used parallels and queued sessions.

  9. Build level search: Searches specific sessions in a build using the build-level search. You can search for a session by its name or ID.

Session view in Automate dashboard

After you click on a particular session in the build view, you will be taken to the session details view of the Automate dashboard as shown in the sample screenshot below: Automate Dashboard Session View

  1. Session name: Displays the spec name. Click Build to return to the builds view.

  2. Session meta: Provides helpful information about the session, such as Browser, OS, Duration, Local testing on/off, Session ID, timestamp, and the user’s name who executed the session.

  3. Logs: Select Text Logs, Console Logs or Screenshots, to view all the steps executed in the test, browser’s JavaScript console output, or the error message captured when the build failed.

  4. Session Video: Captures the recording of the test as it happens in the session. Use this recording to go at a precise point in time when an error occurred and debug.

  5. Input Capabilities: Shows a well-formatted view of the input capabilities that you supplied. These are visible by default and are searchable using the browser’s default find feature.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert