Run Details
Cypress and Playwright run details and metadata - git, environment, execution state
Last updated
Cypress and Playwright run details and metadata - git, environment, execution state
Last updated
When creating a new run, playwright and cypress collect various information about the environment - this information is shown as Run Details in Currents Dashboard.
| Field | Description |
|---|---|
Duration | Run's duration |
Progress | Completed / overall spec files progress |
Started at | Run start timestamp |
Branch | Git branch (or HEAD branch name for GitHub PRs) |
Commit | Git commit message (or PR Title GitHub PRs) |
Browser / Project | Cypress tests browser or Playwright Project |
Author | Git commit author |
CI Build ID |
In order to obtain git data, .git directory should be available during the execution of your tests (on CI machines). The package uses Git commands to get each property, like git show -s --pretty=%B, see src/git-api.js.
In addition, we can detect git information from certain CI-specific environment variables (e.g. GitHub Actions Default Environment Variables).
When git information is not available from .git folder or environment variables, you can provide the data explicitly using environment variables:
Please note: If no git information is available - either from.git folder or from environment variables, no git data will be shown
git information is required for Bitbucket, GitHub and GitLab integrations to work properly
If you're not seeing git information for your runs, most chances it is just not available in the CI environment. Please enable the debug mode for Playwright or Cypress or add git commands to your CI workflow for troubleshooting.
Read more about detecting Pull Requests in GitHub Actions.
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, running the next command @currents/playwright (version 1.7.0+):
or for cypress:
Would generate a run with the corresponding tags:
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 and as part of HTTP Webhooks
