-
Notifications
You must be signed in to change notification settings - Fork 210
docs: Add JUnit5 examples for TestBench9 #1865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need to put a general note in the first chapter of end-to-end part that since Vaadin 24 both JUnit 4 and JUnit 5 test framework versions are supported. Here maybe https://vaadin.com/docs/latest/testing/end-to-end/#features
Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
There will be updates related to testbench update. |
Co-authored-by: Jouni Koivuviita <jouni@vaadin.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few typo corrections.
You can also handle creation and destruction of the WebDriver manually when running on a hub if you don't want to use `ParallelTest` for one reason or another. | ||
In this case, you should create a `RemoteWebdriver` with the correct hub URL and set suitable `DesiredCapabilities` on the driver. | ||
|
||
==== Notes for JUnit 5 | ||
If your test class already creates `WebDriver` implementing `DriverSupplier` you can remove it in favor of automatic driver initialization by TestBench. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If your test class already creates `WebDriver` implementing `DriverSupplier` you can remove it in favor of automatic driver initialization by TestBench. | |
If your test class already creates `WebDriver` implementing `DriverSupplier`, you can remove it in favor of automatic driver initialization by TestBench. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've omitted that one and cannot apply it now :-/
Co-authored-by: Sergey Vinogradov <mr.vursen@gmail.com>
This reverts commit ffd14f0.
Actually, I’ll move Russell’s edits to another branch, so this PR stays focused on the original scope. |
Added JUnit5 examples to present new features of Testbench 9 that will be available with Vaadin 24.
Fixes #1848