Skip to content

chore: Update Chrome (stable) to 137.0.7151.55 #31794

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

Conversation

github-actions[bot]
Copy link
Contributor

This PR was auto-generated to update the version(s) of Chrome for driver tests

Copy link

cypress bot commented May 28, 2025

cypress    Run #62722

Run Properties:  status check passed Passed #62722  •  git commit 2bf85aa7e3: address comments from code review
Project cypress
Branch Review update-chrome-stable-from-136.0.7103.113-beta-from-137.0.7151.40
Run status status check passed Passed #62722
Run duration 18m 29s
Commit git commit 2bf85aa7e3: address comments from code review
Committer Bill Glesias
View all properties for this run ↗︎

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

@AtofStryker AtofStryker self-assigned this May 28, 2025
Copy link
Contributor

@AtofStryker AtofStryker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extension tests are/will fail in 137. We likely need to use chrome for testing in our chrome system tests

@AtofStryker AtofStryker force-pushed the update-chrome-stable-from-136.0.7103.113-beta-from-137.0.7151.40 branch 7 times, most recently from 0726534 to c5795b7 Compare May 28, 2025 17:42
@AtofStryker AtofStryker force-pushed the update-chrome-stable-from-136.0.7103.113-beta-from-137.0.7151.40 branch from c5795b7 to a4375e7 Compare May 28, 2025 19:11
@AtofStryker
Copy link
Contributor

@jennifer-shehane this should now be ready for review

@AtofStryker AtofStryker dismissed their stale review May 28, 2025 20:36

implemented changes. can't re-review

@@ -865,7 +865,11 @@ const systemTests = {
const { browser } = options

if (browser && !customBrowserPath) {
expect(String(browser).toLowerCase()).to.eq(browserName.toLowerCase())
if (browser === 'chrome-for-testing') {
expect(String(browser).toLowerCase()).to.eq(browserName.toLowerCase().replaceAll(' ', '-'))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to replace the spaces?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its checking for chrome for testing because the logic just takes the browser name and makes it lower case, when I have it named chrome-for-testing. Felt better to have the hyphens as the name as its consistent with our current naming

Co-authored-by: Matt Schile <mschile@cypress.io>
@AtofStryker AtofStryker merged commit 08b11b7 into develop May 29, 2025
135 of 137 checks passed
@AtofStryker AtofStryker deleted the update-chrome-stable-from-136.0.7103.113-beta-from-137.0.7151.40 branch May 29, 2025 04:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants