Repository navigation
Docs pass for zero-config + close JUnit 6 pairing gap - #75
Merged
Merged
Conversation
getting-started.md, gradle.md, cloud-execution.md, guides/parallel.md, migration/from-selenium-testng.md and README.md all still told readers to create selenium-boot.yml as a required step, or called its fields required — stale since #66 made the file and every field in it optional with built-in defaults. Updated each to say what actually happens with no file / an omitted field, and marked selenium-boot.yml optional in the two project-structure listings. Also documents that the JUnit 5 bridge now works on JUnit 6 (junit5.md). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
#64 (dependabot) bumped junit-jupiter-api 5.10.2 -> 6.1.3 but left junit-platform-launcher at 1.10.2, leaving the framework's own optional JUnit 5 bridge dependencies on a mismatched pair — flagged since 09-20 as untested for a consumer on JUnit 6. Verified both directions against the selenium-boot-test consumer suite (11/11 real-browser JUnit 5 tests, real Chrome): - consumer on JUnit 5.10.2 + launcher 1.10.2 (unchanged) — still green - consumer on JUnit 6 (jupiter 6.1.3 + launcher 6.1.3) — now green Framework's own unit suite: 525/525 green after the bump. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today's roadmap item (2026-09-22): docs pass for #66's zero-config behavior, plus the JUnit 6 gap flagged in #64.
Docs (zero-config)
getting-started.md,gradle.md,cloud-execution.md,guides/parallel.md,migration/from-selenium-testng.mdandREADME.mdstill presentedselenium-boot.yml(or specific fields in it) as required — stale since #66 shipped built-in defaults. Updated each to say what actually happens with no file / an omitted field.JUnit 6 pairing gap (#64 follow-up)
#64 (dependabot) bumped
junit-jupiter-api5.10.2 → 6.1.3 but leftjunit-platform-launcherat 1.10.2 — flagged in the v3.5.0 changelog draft as untested for a JUnit 6 consumer. Bumpedjunit-platform-launcherto 6.1.3 to match, and verified both pairings against theselenium-boot-testconsumer suite (11/11 real-browser JUnit 5 tests, real Chrome):Framework's own unit suite: 525/525 green after the bump.
junit5.mdnow documents JUnit 6 as supported.CHANGELOG.md's v3.5.0 draft entry updated to reflect the closed gap instead of the open question.
🤖 Generated with Claude Code