Skip to content

Commit 70799ff

Browse files
mshabarovmanolo
andauthored
Add JUnit 6 dependency to getting-started.adoc (#4914)
* Add JUnit 6 dependency to getting-started.adoc Added JUnit 6 dependency for Vaadin TestBench. * more clarifications --------- Co-authored-by: Manuel Carrasco Moñino <[email protected]>
1 parent ad563c1 commit 70799ff

File tree

2 files changed

+10
-4
lines changed

2 files changed

+10
-4
lines changed

articles/flow/testing/end-to-end/getting-started.adoc

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,20 @@ To start using TestBench in an existing project, you need to add the TestBench d
2929
----
3030
[source,xml]
3131
----
32-
<source-info group="JUnit 5 (Since Vaadin 24.0)"></source-info>
32+
<source-info group="JUnit 5/6 (Since Vaadin 24.0 and 25.0 respectively)"></source-info>
3333
<dependency>
3434
<groupId>com.vaadin</groupId>
35-
<artifactId>vaadin-testbench-junit5</artifactId>
35+
<artifactId>vaadin-testbench-junit6</artifactId> <!-- or vaadin-testbench-junit5 -->
3636
<scope>test</scope>
3737
</dependency>
3838
----
3939
--
40+
41+
[NOTE]
42+
====
43+
Starting with Vaadin 25 and Spring Boot 4, the default test framework is JUnit 6 (JUnit Platform). JUnit 6 maintains API compatibility with JUnit 5, so `vaadin-testbench-junit5` and `vaadin-testbench-junit6` work with both, but have transitive JUnit dependencies aligned with the respective versions.
44+
====
45+
4046
The `test` scope and version number are predefined by the Vaadin BOM.
4147

4248
To be able to run tests locally, you might need to install a WebDriver for your browser. See <<installing-webdrivers#,Installing WebDrivers>> for more details.

articles/flow/testing/ui-unit/getting-started.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,15 +34,15 @@ To start creating UI unit tests in an existing project, you need to add the Test
3434
<source-info group="JUnit 5/6"></source-info>
3535
<dependency>
3636
<groupId>com.vaadin</groupId>
37-
<artifactId>vaadin-testbench-unit-junit5</artifactId>
37+
<artifactId>vaadin-testbench-unit-junit6</artifactId> <!-- or vaadin-testbench-unit-junit5 -->
3838
<scope>test</scope>
3939
</dependency>
4040
----
4141
--
4242

4343
[NOTE]
4444
====
45-
Starting with Vaadin 25 and Spring Boot 4, the default test framework is JUnit 6 (JUnit Platform). JUnit 6 maintains API compatibility with JUnit 5, so `vaadin-testbench-unit-junit5` works with both.
45+
Starting with Vaadin 25 and Spring Boot 4, the default test framework is JUnit 6 (JUnit Platform). JUnit 6 maintains API compatibility with JUnit 5, so `vaadin-testbench-unit-junit5` and `vaadin-testbench-unit-junit6` work with both, but have transitive JUnit dependencies aligned with the respective versions.
4646
4747
For JUnit 4 tests using [classname]`UIUnit4Test`, the `junit-vintage-engine` dependency is required because JUnit 6 doesn't natively execute JUnit 4 tests. Without it, tests won't be detected or executed.
4848

0 commit comments

Comments
 (0)