EDIT

The primary option to setup a test suite for testing the cdm-vaadin UIs is to use the Vaadin Test Bench. Even if this product is open source (https://github.com/vaadin/testbench) it is a commercial product and purchasing a proper license seems required for using it even if the test bench can be compiled from source.

The major benefits of the Vaadin Test Bench over plain selenium seems to be:

1. integrates application startup
2. can run on a hub or parallelized -
3. has "intelligent" wait() functionality "In pure Selenium, you need to use the wait methods explicitly, and know what to use and when. Vaadin TestBench works together with the client-side engine of Vaadin framework to immediately detect when the rendering is finished. Waiting is implicit, so you do not normally need to insert any wait commands yourself." (Book of Vaadin chapter 23.8.1. Waiting for Vaadin). This functionality is provided by the com.vaadin.testbench.commands.TestBenchCommandExecutor.waitForVaadin(). The waitForVaadin method is automatically called when specific WebDriver methods are invoked. The DriverInvocationHandler cares for this.
4. Selenium Element for each of the Vaadin UI components

Options to replace the Vaadin Test Bench magic by own developments (number in the list correspond to the numbers above)

1. starting of jetty before maven integration test and to stop it afterwards is quite easy to setup
2. no need to do this in the test framework itself. Jenkins provides much better means to do that.
3. The intelligent wait could be easily replaced by an own implementation
4. not urgently needed

More details on the vaadin TestBench can be found in the master thesis for which the TestBench has been developed: rogozin.pdf

An alternative is to use selenium directly on the vaadin ui as demonstrated by the selenide project demo, Selenide by the way is an alternative to Selenium which promises to be simpler to use. Selenide code is at github:codeborne/selenide

More on selenide/vaadin:

• https://github.com/appreciated/vaadin-selenide-spring-example

Setting up test web application context with spring boot:

https://blog.ccbill.com/spring-boot-and-context-handling

Testdata¶

Testadata management either per DbUnit or spring-test:

spring-test

https://stackoverflow.com/questions/34617152/how-to-re-create-database-before-each-test-in-spring#37246354

e.g.:

@Transactional(value=JpaConfiguration.TRANSACTION_MANAGER_NAME)
@Sql(executionPhase=ExecutionPhase.BEFORE_TEST_METHOD,scripts="classpath:/test-sql/group2.sql")
public class GroupServiceTest extends TimeoffApplicationTests {

Related projects and frameworks:

• Selenium addon for Vaadin: It supports an abstraction layer to easily read / write and assert value inside fields.
  • https://github.com/thomasletsch/selenium-addon
  • https://vaadin.com/directory/component/selenium-addon-for-vaadin

General considerations on tests

• https://dzone.com/articles/8-test-automation-anti-patterns-and-how-to-avoid-t