[test] Add simple test with Java binding and enable BiDi

[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

Tests

---

Description

• Add Java-based Selenium tests with BiDi support

• Integrate Java tests into CI/CD workflows

• Create test infrastructure for all browsers

• Enable modern RemoteWebDriver patterns

---

Changes diagram

flowchart LR
  A["Java Test Suite"] --> B["Bootstrap Script"]
  B --> C["Docker Container"]
  C --> D["Selenium Grid"]
  D --> E["Browser Tests"]
  F["CI Workflows"] --> B
  G["Makefile"] --> B

Loading

---

Changes walkthrough 📝

	Relevant files
Tests	6 files bootstrap_java.sh Create Java test bootstrap script                                                +34/-0    release-chrome-versions.yml Add Java tests to Chrome workflow                                                +2/-1      release-edge-versions.yml Add Java tests to Edge workflow                                                    +2/-1      release-firefox-versions.yml Add Java tests to Firefox workflow                                              +2/-1      Makefile Add Java test targets for browsers                                              +33/-1    SeleniumTests.java Implement Java Selenium tests with BiDi                                    +92/-0
Documentation	1 files README.md Add Java test documentation                                                            +24/-0
Configuration changes	3 files gradle-wrapper.properties Configure Gradle wrapper properties                                            +7/-0      gradlew Add Gradle wrapper script                                                                +251/-0  gradlew.bat Add Gradle wrapper batch script                                                    +94/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The script uses exit_code=$? to capture the exit code from gradlew but doesn't handle the case where the variable might not be set if the script exits before line 34. The cleanup function references this variable which could be undefined. function cleanup { echo "Stopping the Selenium Grid container..." docker rm -f standalone || true exit $exit_code } Package Declaration The package declaration dev.selenium doesn't match the file structure. The test file is located in the default package but declares a specific package, which could cause compilation issues. package dev.selenium; Test Assertions Using basic assert statements instead of JUnit assertions reduces test readability and debugging capabilities. JUnit assertions provide better error messages and are the standard practice. assert header.contains("A/B Test"); } @Test void checkboxesCanBeToggled() { driver.get("https://the-internet.herokuapp.com/checkboxes"); WebElement checkbox1 = driver.findElements(By.cssSelector("input[type='checkbox']")).get(0); boolean initialState = checkbox1.isSelected(); checkbox1.click(); assert checkbox1.isSelected() != initialState; } @Test void dropdownSelectionWorks() { driver.get("https://the-internet.herokuapp.com/dropdown"); WebElement dropdown = driver.findElement(By.id("dropdown")); Select select = new Select(dropdown); select.selectByVisibleText("Option 2"); assert select.getFirstSelectedOption().getText().equals("Option 2");

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Fix exit code handling The script doesn't properly handle the exit code from the cleanup function. The exit_code variable is set after ./gradlew clean test but the cleanup function references it before it's defined, which could cause undefined behavior. tests/SeleniumJavaTests/bootstrap_java.sh [34] exit_code=$? +exit $exit_code Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that the exit_code variable is uninitialized if the script fails before the tests run, causing the script to incorrectly exit with status 0.	Medium
General	Replace assert with JUnit assertions Using assert statements for test assertions is problematic because they can be disabled with -da JVM flag and don't provide meaningful error messages. Use JUnit assertions instead for proper test failure reporting. tests/SeleniumJavaTests/src/test/java/SeleniumTests.java [65-83] -assert header.contains("A/B Test"); +import static org.junit.jupiter.api.Assertions.*; + +assertTrue(header.contains("A/B Test")); ... -assert checkbox1.isSelected() != initialState; +assertNotEquals(initialState, checkbox1.isSelected()); ... -assert select.getFirstSelectedOption().getText().equals("Option 2"); +assertEquals("Option 2", select.getFirstSelectedOption().getText()); [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly points out that using JUnit assertions is better practice than native assert statements for tests, as they provide more informative failure messages and are not disabled by default.	Medium
More