chore(deps): update dependency rubocop-rspec to v3.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rubocop-rspec (changelog)	3.1.0 -> 3.2.0

---

Release Notes

rubocop/rubocop-rspec (rubocop-rspec)

v3.2.0

Compare Source

• Fix RSpec/VoidExpect to only operate inside an example block. ([@​corsonknowles])
• Change RSpec/ContextWording cop to always report an offense when both Prefixes and AllowedPatterns are empty. ([@​ydah])
• Add support for and and or compound matchers to RSpec/ChangeByZero cop. ([@​ydah])

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	a2f1e03
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/6724d45aff0182000818853f
😎 Deploy Preview	https://deploy-preview-2014--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codiumai-pr-agent-pro]

CI Failure Feedback 🧐

(Checks updated until commit a2f1e03)

Action: tests (ubuntu, stable)

Failed stage: Run tests [❌]

Failed test name: Mouse move by offset offset from viewport

Failure summary: The action failed because the test Mouse move by offset offset from viewport did not pass. The test failed because the expected x-coordinate was not within the acceptable range: The test expected the x-coordinate to be within 1 unit of 8. However, the actual x-coordinate was 630, which is significantly outside the expected range.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 282: timeout_minutes: 20 283: max_attempts: 3 284: command: cd examples/ruby 285: bundle exec rspec 286: 287: retry_wait_seconds: 10 288: polling_interval_seconds: 1 289: warning_on_retry: true 290: continue_on_error: false ... 471: �[0KDownloading selenium-server-4.26.0.jar: 97% (41625216 / 42632726) 472: �[0KDownloading selenium-server-4.26.0.jar: 98% (41870976 / 42632726) 473: �[0KDownloading selenium-server-4.26.0.jar: 98% (42106457 / 42632726) 474: �[0KDownloading selenium-server-4.26.0.jar: 99% (42352217 / 42632726) 475: �[0KDownloading selenium-server-4.26.0.jar: 99% (42597977 / 42632726).......*******..........**************............................. 476: Pending: (Failures listed here are expected and do not affect your suite's status) 477: 1) Keys copy and paste 478: # Test guarded; Guarded by {:browser=>:chrome, :reason=>"https://bugs.chromium.org/p/chromedriver/issues/detail?id=4264"}; 479: Failure/Error: expect(driver.find_element(id: 'textInput').attribute('value')).to eq 'SeleniumSelenium!' ... 607: 43) Element Locators with relative locators finds near element 608: # These are reference following the documentation example 609: # ./spec/elements/locators_spec.rb:55 610: 44) Element Locators with relative locators chains relative locators 611: # These are reference following the documentation example 612: # ./spec/elements/locators_spec.rb:59 613: Failures: 614: 1) Mouse move by offset offset from viewport 615: Failure/Error: expect(x_coord).to be_within(1).of(8) 616: expected 630 to be within 1 of 8 617: # ./spec/actions_api/mouse_spec.rb:119:in `block (3 levels) in <top (required)>' 618: Finished in 4 minutes 14.1 seconds (files took 2.78 seconds to load) 619: 185 examples, 1 failure, 44 pending 620: Failed examples: 621: rspec ./spec/actions_api/mouse_spec.rb:111 # Mouse move by offset offset from viewport 622: ##[warning]Attempt 1 failed. Reason: Child_process exited with error code 1 623: ......*..........F..............................................................***...*****************.....*........*.......*******..........**************............................. 624: Pending: (Failures listed here are expected and do not affect your suite's status) 625: 1) Keys copy and paste 626: # Test guarded; Guarded by {:browser=>:chrome, :reason=>"https://bugs.chromium.org/p/chromedriver/issues/detail?id=4264"}; 627: Failure/Error: expect(driver.find_element(id: 'textInput').attribute('value')).to eq 'SeleniumSelenium!' ... 755: 43) Element Locators with relative locators finds near element 756: # These are reference following the documentation example 757: # ./spec/elements/locators_spec.rb:55 758: 44) Element Locators with relative locators chains relative locators 759: # These are reference following the documentation example 760: # ./spec/elements/locators_spec.rb:59 761: Failures: 762: 1) Mouse move by offset offset from viewport 763: Failure/Error: expect(x_coord).to be_within(1).of(8) 764: expected 630 to be within 1 of 8 765: # ./spec/actions_api/mouse_spec.rb:119:in `block (3 levels) in <top (required)>' 766: Finished in 3 minutes 31.9 seconds (files took 1.3 seconds to load) 767: 185 examples, 1 failure, 44 pending 768: Failed examples: 769: rspec ./spec/actions_api/mouse_spec.rb:111 # Mouse move by offset offset from viewport 770: ##[warning]Attempt 2 failed. Reason: Child_process exited with error code 1 771: ......*..........F..............................................................***...*****************.....*........*.......*******..........**************............................. 772: Pending: (Failures listed here are expected and do not affect your suite's status) 773: 1) Keys copy and paste 774: # Test guarded; Guarded by {:browser=>:chrome, :reason=>"https://bugs.chromium.org/p/chromedriver/issues/detail?id=4264"}; 775: Failure/Error: expect(driver.find_element(id: 'textInput').attribute('value')).to eq 'SeleniumSelenium!' ... 903: 43) Element Locators with relative locators finds near element 904: # These are reference following the documentation example 905: # ./spec/elements/locators_spec.rb:55 906: 44) Element Locators with relative locators chains relative locators 907: # These are reference following the documentation example 908: # ./spec/elements/locators_spec.rb:59 909: Failures: 910: 1) Mouse move by offset offset from viewport 911: Failure/Error: expect(x_coord).to be_within(1).of(8) 912: expected 630 to be within 1 of 8 913: # ./spec/actions_api/mouse_spec.rb:119:in `block (3 levels) in <top (required)>' 914: Finished in 3 minutes 33 seconds (files took 1.39 seconds to load) 915: 185 examples, 1 failure, 44 pending 916: Failed examples: 917: rspec ./spec/actions_api/mouse_spec.rb:111 # Mouse move by offset offset from viewport 918: ##[error]Final attempt failed. Child_process exited with error code 1

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.