Skip to content

Use Firefox for system specs#6230

Merged
tvdeyen merged 1 commit intosolidusio:mainfrom
mamhoff:use-firefox-for-system-specs
May 9, 2025
Merged

Use Firefox for system specs#6230
tvdeyen merged 1 commit intosolidusio:mainfrom
mamhoff:use-firefox-for-system-specs

Conversation

@mamhoff
Copy link
Contributor

@mamhoff mamhoff commented May 6, 2025

Summary

Chrome seems to consistently get updated with new interesting options,
and our specs have been sometimes more, and sometimes less flaky with
Chrome as the browser that drives our system specs.

This change uses the preconfigured selenium_headless driver from the
Selenium gem, which uses Firefox under the hood.

There are a few changes to helpers in the new admin. All of them have to
with clicking table cells rather than the underlying table row. This is
how real users also interact with the respective page, so I think it's a
good change.

Checklist

Check out our PR guidelines for more details.

The following are mandatory for all PRs:

The following are not always needed:

  • 📖 I have updated the README to account for my changes.
  • 📑 I have documented new code with YARD.
  • 🛣️ I have opened a PR to update the guides.
  • ✅ I have added automated tests to cover my changes.
  • 📸 I have attached screenshots to demo visual changes.

@mamhoff mamhoff requested a review from a team as a code owner May 6, 2025 12:49
@github-actions github-actions bot added changelog:solidus_backend Changes to the solidus_backend gem changelog:solidus_core Changes to the solidus_core gem labels May 6, 2025
@mamhoff mamhoff force-pushed the use-firefox-for-system-specs branch 2 times, most recently from 78100e4 to 5155d17 Compare May 6, 2025 13:54
@github-actions github-actions bot added changelog:solidus_admin and removed changelog:solidus_backend Changes to the solidus_backend gem labels May 6, 2025
@mamhoff mamhoff force-pushed the use-firefox-for-system-specs branch 3 times, most recently from a72bfa0 to f9a17b3 Compare May 7, 2025 07:25
@codecov
Copy link

codecov bot commented May 7, 2025

Codecov Report

Attention: Patch coverage is 33.33333% with 4 lines in your changes missing coverage. Please review.

Project coverage is 88.87%. Comparing base (61f675e) to head (d0f8c07).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
core/lib/spree/testing_support/capybara_driver.rb 0.00% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6230      +/-   ##
==========================================
+ Coverage   88.80%   88.87%   +0.06%     
==========================================
  Files         842      842              
  Lines       18244    18230      -14     
==========================================
  Hits        16202    16202              
+ Misses       2042     2028      -14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mamhoff mamhoff force-pushed the use-firefox-for-system-specs branch from f9a17b3 to 866af70 Compare May 7, 2025 15:10
Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

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

I am not opposed to using Firefox by default, but we should be transparent about it.

@mamhoff mamhoff force-pushed the use-firefox-for-system-specs branch from 866af70 to d0f8c07 Compare May 9, 2025 12:41
@tvdeyen tvdeyen changed the title Add Firefox Drivers to capybara_driver.rb Use Firefox for system specs May 9, 2025
Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

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

Nice. Thanks

Chrome seems to consistently get updated with new interesting options,
and our specs have been sometimes more, and sometimes less flaky with
Chrome as the browser that drives our system specs.

This change uses the preconfigured `selenium_headless` driver from the
Selenium gem, which uses Firefox under the hood.

There are a few changes to helpers in the new admin. All of them have to
with clicking table cells rather than the underlying table row. This is
how real users also interact with the respective page, so I think it's a
good change.
@tvdeyen tvdeyen force-pushed the use-firefox-for-system-specs branch from d0f8c07 to d5694a1 Compare May 9, 2025 15:52
@tvdeyen tvdeyen enabled auto-merge May 9, 2025 15:52
@tvdeyen tvdeyen merged commit 5c415e7 into solidusio:main May 9, 2025
21 of 22 checks passed
mamhoff added a commit to mamhoff/solidus_dev_support that referenced this pull request May 15, 2025
Solidus core has migrated to using Firefox for headless testing, which seems to
be more stable than Chrome, and uses minimal configuration.

See solidusio/solidus#6230
@tvdeyen tvdeyen added backport-v4.1 Backport this pull-request to v4.1 backport-v4.2 Backport this pull-request to v4.2 backport-v4.3 Backport this pull-request to v4.3 backport-v4.4 Backport this pull-request to v4.4 backport-v4.5 Backport this pull-request to v4.5 labels May 30, 2025
@github-actions
Copy link

💔 All backports failed

Status Branch Result
v4.1 Backport failed because of merge conflicts
v4.2 Backport failed because of merge conflicts
v4.3 Backport failed because of merge conflicts
v4.4 Backport failed because of merge conflicts
v4.5 Backport failed because of merge conflicts

You might need to backport the following PRs to v4.5:
- Merge pull request #6227 from mamhoff/no-javascripts-in-dummy-apps

Manual backport

To create the backport manually run:

backport --pr 6230

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@github-actions
Copy link

💔 All backports failed

Status Branch Result
v4.1 Backport failed because of merge conflicts
v4.2 Backport failed because of merge conflicts
v4.3 Backport failed because of merge conflicts
v4.4 Backport failed because of merge conflicts
v4.5 Backport failed because of merge conflicts

You might need to backport the following PRs to v4.5:
- Merge pull request #6227 from mamhoff/no-javascripts-in-dummy-apps

Manual backport

To create the backport manually run:

backport --pr 6230

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@github-actions
Copy link

💔 All backports failed

Status Branch Result
v4.1 Backport failed because of merge conflicts
v4.2 Backport failed because of merge conflicts
v4.3 Backport failed because of merge conflicts
v4.4 Backport failed because of merge conflicts
v4.5 Backport failed because of merge conflicts

You might need to backport the following PRs to v4.5:
- Merge pull request #6227 from mamhoff/no-javascripts-in-dummy-apps

Manual backport

To create the backport manually run:

backport --pr 6230

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@github-actions
Copy link

💔 All backports failed

Status Branch Result
v4.1 Backport failed because of merge conflicts
v4.2 Backport failed because of merge conflicts
v4.3 Backport failed because of merge conflicts
v4.4 Backport failed because of merge conflicts
v4.5 Backport failed because of merge conflicts

You might need to backport the following PRs to v4.5:
- Merge pull request #6227 from mamhoff/no-javascripts-in-dummy-apps

Manual backport

To create the backport manually run:

backport --pr 6230

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@github-actions
Copy link

💔 All backports failed

Status Branch Result
v4.1 Backport failed because of merge conflicts
v4.2 Backport failed because of merge conflicts
v4.3 Backport failed because of merge conflicts
v4.4 Backport failed because of merge conflicts
v4.5 Backport failed because of merge conflicts

You might need to backport the following PRs to v4.5:
- Merge pull request #6227 from mamhoff/no-javascripts-in-dummy-apps

Manual backport

To create the backport manually run:

backport --pr 6230

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@tvdeyen tvdeyen removed backport-v4.1 Backport this pull-request to v4.1 backport-v4.2 Backport this pull-request to v4.2 backport-v4.3 Backport this pull-request to v4.3 backport-v4.4 Backport this pull-request to v4.4 labels May 30, 2025
@tvdeyen
Copy link
Member

tvdeyen commented May 30, 2025

💚 All backports created successfully

Status Branch Result
v4.5

Questions ?

Please refer to the Backport tool documentation

mamhoff added a commit to mamhoff/solidus_dev_support that referenced this pull request Aug 1, 2025
Solidus core has migrated to using Firefox for headless testing, which seems to
be more stable than Chrome, and uses minimal configuration.

See solidusio/solidus#6230

Because older versions of Solidus might not have the new
`capybara_driver.rb` file, we still include the legacy code in a
`rescue` block.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-v4.5 Backport this pull-request to v4.5 changelog:solidus_admin changelog:solidus_core Changes to the solidus_core gem

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants