Run Details

Cypress run details and metadata - git data, environment
When creating a new run, cypress agents collect various information about their environment - this information is shown as Run Details in Currents Dashboard.
Cypress run details example
Run's duration
Completed / overall spec files progress
Started at
Run start timestamp
GIt remote origin
Git branch
Git commit message
Cypress tests browser
Git commit author
CI Build ID

Cypress Run Git Information

Internally, cypress uses npm package for fetching git information.
In order to to obtain git data, .git folder should be available during execution of your cypress tests (on CI machines). The package uses Git commands to get each property, like git show -s --pretty=%B, see src/git-api.js.
When git information is not available from .git folder. you can provide fallback environment variables:
COMMIT_INFO_MESSAGE: commit message
COMMIT_INFO_EMAIL: commit author email
COMMIT_INFO_AUTHOR: commit author name
COMMIT_INFO_SHA: commit info sha
COMMIT_INFO_TIMESTAMP: commit timestamp
COMMIT_INFO_REMOTE: remote origin
Please note: If no git information is available - either from.git folder or from environment variables, no information or default placeholder data will be shown
Please note: git information is required for Bitbucket, GitHub and Gitlab integrations to work properly

Run Tags

Tagging is a convenient way to augment your executions with extra data that can be helpful for managing your tests. You can tag the runs (executions) by adding --tag tagA,tagB flag to currents command.
For example, issues the next command:
currents run --parallel --record --tag currents-cli,gha
Would generate a run with the corresponding tags:
Tagged run example
The run, spec and test execution recordings will inherit the tags. You can use the tags as a filter when browsing the dashboard to narrow down the results, for example:
  • filter runs by tags
  • filter insights and analytics to only include records with a particular tag
  • filter errors, tests and spec performance explorers to only include records with a particular tag
The tags are also available in the results returned from the API and as part of HTTP Webhooks
Example of filterin Run Status Metrics by Tags