All Implemented Interfaces:

TesterWrappers

Direct Known Subclasses:

SpringUIUnit4Test

Base JUnit 4 class for UI unit tests. The class automatically scans classpath for routes and error views. Subclasses should typically restrict classpath scanning to a specific packages for faster bootstrap, by using ViewPackages annotation. If the annotation is not present a full classpath scan is performed

 {@code
 @ViewPackages(classes = {CartView.class, CheckoutView.class})
 public class CartViewTest extends UIUnit4Test {
 }

 @ViewPackages(packages = {"com.example.shop.cart", "com.example.security"})
 public class CartViewTest extends UIUnit4Test {
 }

 @ViewPackages(
    classes = {CartView.class, CheckoutView.class},
    packages = {"com.example.security"}
 )
 public class CartViewTest extends UIUnit4Test {
 }
 </pre>


 Set up of Vaadin environment is performed before each test by {@link
 #initVaadinEnvironment()} method, and will be executed before {@code @Before}
 methods defined in subclasses. At the same way, cleanup tasks operated by
 {@link #cleanVaadinEnvironment()} are executed after each test, and after all
 {@code @After} annotated methods in subclasses.

 Custom Flow service implementations supported by {@link
 com.vaadin.flow.di.Lookup} SPI can be provided overriding {@link
 #initVaadinEnvironment()} and passing to super implementation the service
 classes that should be initialized during setup.

 <pre>
 {@code
 &#64;Override
 public void initVaadinEnvironment() {
     super.initVaadinEnvironment(CustomInstantiatorFactory.class);
 }
 }
 </pre>
 <p/>
 To get a graphical ascii representation of the UI tree on failure override
 the {@link #printTree()} method to return true.