[ci] Update deps version

[VietND96]

User description

Thanks for contributing to the Docker-Selenium project!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines, applied for this repository.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Enhancement

---

Description

• Update Python base image from 3.11 to 3.14

• Modernize test environment dependencies

---

Diagram Walkthrough

flowchart LR
  A["tests/Dockerfile"] -- "Update base image" --> B["python:3.14-slim"]

Loading

File Walkthrough

	Relevant files
Dependencies	Dockerfile Update Python base image version                                                  tests/Dockerfile Update base image from python:3.11-slim to python:3.14-slim Modernize Python runtime version for test environment +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Unpinned base image Description: Bumping the base image to 'python:3.14-slim' may unintentionally pull an unpinned, moving latest patch which can change over time, leading to supply-chain drift and reproducibility risks. Dockerfile [1-1] Referred Code FROM python:3.14-slim
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit logs: The added change does not introduce or modify any application logic to log critical actions, making it impossible to verify audit trail coverage from this diff alone. Referred Code FROM python:3.14-slim Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error handling: The PR only updates the base image in a Dockerfile and adds no executable logic to assess error handling or edge case management. Referred Code FROM python:3.14-slim Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Input validation: The diff only changes the base image to python:3.14-slim without touching input paths, so validation and secure handling cannot be evaluated from this change alone. Referred Code FROM python:3.14-slim Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Use a valid Docker base image Replace the invalid Docker base image python:3.14-slim with a valid one, such as python:3.12-slim, as Python 3.14 has not yet been released. tests/Dockerfile [1] -FROM python:3.14-slim +FROM python:3.12-slim Apply / Chat Suggestion importance[1-10]: 10 __ Why: The suggestion correctly identifies that python:3.14-slim is an invalid base image, which will cause the Docker build to fail, making this a critical fix.	High
Update