chore(deps): update dependency org.junit.jupiter:junit-jupiter-engine to v5.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.junit.jupiter:junit-jupiter-engine (source)	5.10.3 -> 5.11.0

---

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 these updates 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	dd793b4
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/66bcbd91e6b4d60008ec48dc
😎 Deploy Preview	https://deploy-preview-1858--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.

[qodo-merge-pro]

CI Failure Feedback 🧐

Action: tests (ubuntu)

Failed stage: Install Edge for set binary test [❌]

Failure summary: The action failed because it could not find the required artifact for Edge stable on the Linux amd64 platform. This indicates that the download attempt for Edge stable was unsuccessful due to the artifact being unavailable.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 146: edge-version: stable 147: env: 148: DISPLAY: :99 149: GITHUB_TOKEN: *** 150: GH_TOKEN: *** 151: ##[endgroup] 152: Setup Edge stable 153: Attempting to download Edge stable... 154: ##[error]Artifact not found of Edge stable for platform linux amd64

---

✨ 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.