Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show Node version in Cypress Cloud #25581

Open
dangowans opened this issue Jan 25, 2023 · 1 comment
Open

Show Node version in Cypress Cloud #25581

dangowans opened this issue Jan 25, 2023 · 1 comment
Assignees
Labels
Cypress Cloud Feature request or issue in Cypress Cloud, not App Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. type: feature New feature that does not currently exist

Comments

@dangowans
Copy link

dangowans commented Jan 25, 2023

What would you like?

When looking at the results of my Cypress runs, I see the browser, the operating system, and the Cypress version used for the run, but I'd like to see the version of Node used as well.

Why is this needed?

I updated my testing workflow on GitHub Actions to test with Node 14, 16, and 18. Unfortunately, I can't differentiate the runs now.

image

Other

Workflow Run:
https://github.com/cityssm/lot-occupancy-system/actions/runs/4009458612

Cypress Run Results Page:
https://cloud.cypress.io/projects/xya1fn/runs

@dangowans
Copy link
Author

While I still think having the Node version tracked as part of the run would be helpful, I found a workaround for me using the --tag parameter when running Cypress.

When running Cypress from one of my Mocha tests, I use the following command

cypress run --config-file cypress.config.js --browser ${browser} --tag "${browser},${process.version}"

browser is either firefox or chrome. process.version is the running version of Node.

Now my runs are easy to differentiate.

image

@nagash77 nagash77 added type: feature New feature that does not currently exist routed-to-cloud Cypress Cloud Feature request or issue in Cypress Cloud, not App labels Jan 27, 2023
@nagash77 nagash77 added Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. and removed routed-to-cloud labels Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cypress Cloud Feature request or issue in Cypress Cloud, not App Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. type: feature New feature that does not currently exist
Projects
None yet
Development

No branches or pull requests

4 participants