Skip to content

internal: only capture anonymous studio started analytics when cloud studio is disabled #31665

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

Merged
merged 1 commit into from
May 8, 2025

Conversation

astone123
Copy link
Contributor

Follow-up for https://github.com/cypress-io/cypress-services/issues/10501

Additional details

We only want to capture the studio started event if the user does not have cloud studio enabled.

Steps to test

How has the user experience changed?

PR Tasks

@astone123 astone123 requested a review from ryanthemanuel May 8, 2025 13:07
@astone123 astone123 self-assigned this May 8, 2025
Copy link

cypress bot commented May 8, 2025

cypress    Run #62265

Run Properties:  status check passed Passed #62265  •  git commit f1ca10c6df: internal: only capture anonymous studio started analytics when cloud studio is d...
Project cypress
Branch Review studio-analytics
Run status status check passed Passed #62265
Run duration 14m 42s
Commit git commit f1ca10c6df: internal: only capture anonymous studio started analytics when cloud studio is d...
Committer astone123
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 10
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 590
View all changes introduced in this branch ↗︎
UI Coverage  0%
  Untested elements 4  
  Tested elements 0  
Accessibility  97.09%
  Failed rules  0 critical   1 serious   0 moderate   0 minor
  Failed elements 6  

@astone123 astone123 merged commit c205145 into develop May 8, 2025
91 of 93 checks passed
@astone123 astone123 deleted the studio-analytics branch May 8, 2025 13:59
@cypress-bot
Copy link
Contributor

cypress-bot bot commented May 20, 2025

Released in 14.4.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v14.4.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators May 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants