Restructure browserless testing docs for Spring Boot users#5233
Open
Restructure browserless testing docs for Spring Boot users#5233
Conversation
Member
Artur-
commented
Feb 25, 2026
- Rewrite the Getting Started guide to assume Spring Boot by default, with a self-contained example that walks through key concepts (navigating, direct Java API access, testers, component queries)
- Extract content into dedicated pages: Component Testers (using built-in + building custom), Optimizing Tests (@viewpackages, @ContextConfiguration), Spring Security Testing, and rename the Spring page to Non-Spring Projects
- Fix typos and improve prose throughout the browserless testing section (index, component-query, quarkus pages)
Most Vaadin users use Spring Boot, so the getting started guide now assumes Spring Boot by default. The old Spring page becomes "Non-Spring Projects" for plain Java, and Spring Security testing content is extracted into its own page.
Restructure getting-started to explain key concepts after the first test example: direct Java API access, component testers, and finder methods. Move @viewpackages and @ContextConfiguration content to a dedicated "Optimizing Tests" page.
Remove MainLayout reference and layout boilerplate so the example compiles without extra classes in a fresh project.
Explain that package-protected fields require placing the test class in the same Java package under src/test as the view in src/main.
Move the custom testers section out of component-query.adoc into a new component-testers.adoc page (order: 18) that covers both using built-in testers and building custom ones. Add cross-reference from getting-started.
mcollovati
reviewed
Feb 25, 2026
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.