Skip to content

Restructure browserless testing docs for Spring Boot users#5233

Open
Artur- wants to merge 8 commits intomainfrom
docs-tune-browserless
Open

Restructure browserless testing docs for Spring Boot users#5233
Artur- wants to merge 8 commits intomainfrom
docs-tune-browserless

Conversation

@Artur-
Copy link
Member

@Artur- 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.
@Artur- Artur- requested a review from mcollovati February 25, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants