Skip to content

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

Merged
merged 17 commits into from
Nov 29, 2022
Merged

docs: Add JUnit5 examples for TestBench9 #1865

merged 17 commits into from
Nov 29, 2022

Conversation

MarcinVaadin
Copy link
Member

@MarcinVaadin MarcinVaadin commented Nov 4, 2022

Added JUnit5 examples to present new features of Testbench 9 that will be available with Vaadin 24.

Fixes #1848

@aws-amplify-eu-west-1
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1865.dcmp4ajsd49kq.amplifyapp.com

Copy link
Contributor

@mshabarov mshabarov left a 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

MarcinVaadin and others added 3 commits November 7, 2022 12:17
Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
@MarcinVaadin MarcinVaadin marked this pull request as draft November 8, 2022 11:08
@MarcinVaadin
Copy link
Member Author

There will be updates related to testbench update.

@MarcinVaadin MarcinVaadin marked this pull request as ready for review November 10, 2022 08:35
@MarcinVaadin MarcinVaadin requested a review from jouni November 16, 2022 19:33
Copy link
Contributor

@vursen vursen left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Member Author

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>
@MarcinVaadin MarcinVaadin requested a review from vursen November 17, 2022 08:19
@russelljtdyer russelljtdyer added Language checked English language and AsciiDoc formatting checks done and removed Language not checked labels Nov 29, 2022
@jouni
Copy link
Member

jouni commented Nov 29, 2022

Actually, I’ll move Russell’s edits to another branch, so this PR stays focused on the original scope.

@jouni jouni merged commit 71924c8 into latest Nov 29, 2022
@jouni jouni deleted the docs/testbench-junit5 branch November 29, 2022 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Language checked English language and AsciiDoc formatting checks done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation for JUnit 5 support in TestBench end-to-end testing
6 participants