testbench
testbench copied to clipboard
Vaadin TestBench is a tool for automated user interface testing of Vaadin applications.
Create a [Tester](https://github.com/vaadin/testbench/blob/main/vaadin-testbench-unit-shared/src/main/java/com/vaadin/testbench/unit/ComponentTester.java) class for [VirtualList](https://github.com/vaadin/flow-components/tree/main/vaadin-virtual-list-flow-parent)
The expression `$(ButtonWrapper.class).first()` should fundamentally not be used in a test: it promotes creation of flaky tests. If there are multiple Buttons on the web page, TestBench selects an arbitrary...
There are several occasions where [testbench prints to stdout](https://github.com/search?q=repo%3Avaadin%2Ftestbench%20println&type=code) While not harmful, it's slightly annoying for those trying to control test run output through slf4j etc mechanisms.
`AbstractBrowserTestBase::assertEquals(WebElement, WebElement)` should be deprecated as it is an obsolete workaround for `TestBenchElement` that formerly lacked an implementation for `equals` to correctly compare "wrapped" elements. That issue was resolved with...
When creating a UI unit test for a Grid that uses a template renderer (i.e. `LitRenderer` or the deprecated `TemplateRenderer`), it's useful to find `withProperty` values that were assigned for...
We want to define a set of custom testers for a huge set of UI Unit tests. Each of those UI Unit tests is going to extend from a custom...
Currently, Testbench `@BrowserConfiguration` does not work correctly with JUnit `@Nested` annotation that is meant to work with not-static inner classes. The problem is that when `BrowserExtension.evaluateExecutionCondition` evaluates whether the test...
Migrating from Junit4 based Testbench to the Junit5 based Testbench, I noticied that all tests are now executed in parallel - resulting in multiple errors with tests that using the...
Currently, a UI Unit Test always navigates to the main route (blank path), then in the test the developer can navigate to another view before starting assertions. It would be...
This [PR](https://github.com/vaadin/flow/pull/14034) improved the UI class by adding navigation methods that take query parameters. UI Unit Test base class should also provide such helpers.