Comment on page
Run Details
Cypress and Playwright run details and metadata - git, environment, execution state
When creating a new run, playwright and cypress collect various information about the environment - this information is shown as Run Details in Currents Dashboard.
Cypress run details example
Field | Description |
|---|---|
Duration | Run's duration |
Progress | Completed / overall spec files progress |
Started at | Run start timestamp |
Origin | GIt remote origin |
Branch | Git branch |
Commit | Git commit message |
Browser / Project | Cypress tests browser or Playwright Project |
Author | Git commit author |
CI Build ID |
In order to to obtain git data,
.git folder 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:COMMIT_INFO_BRANCH: branch
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 git data will be shown git information is required for Bitbucket, GitHub and GitLab integrations to work properlyIf 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.
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+):npx pwc --key RECORD_KEY --project-id PROJECT_ID --ci-build-id CI_BUILD_ID --tag currents-cli,gha
or for cypress:
cypress-cloud 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
Example of filterin Run Status Metrics by Tags
Last modified 1mo ago