Add maven based server tests for Wildfly and Jetty (#10116)

This patch refactors the generic integration test war into 
two jar dependencies and individual modules for different servers.

There is now a common approach for making configurations for the
remaining server tests still executed through an Ant build script.

1 files changed, 21 insertions, 2 deletions

diff --git a/test/README.md b/test/README.md
index ca9e61c57c..b89a34da49 100644
--- a/test/README.md
+++ b/test/README.md
@@ -1,5 +1,24 @@
+# Vaadin Test
+
 This is a test project to verify the basic functionality of various related plugins and addons.
 
-To validate a given Vaadin Version, run `mvn clean verify -Dvaadin.version=VERSIONNUMBER`
+## General use
+
+To validate a given Vaadin Version, run `mvn clean verify -Dvaadin.version=VERSIONNUMBER`.
+
+## Server testing
+
+To validate only server compatibility, run `mvn clean verify -Dvaadin.version=VERSIONNUMBER` in the `servlet-containers` module.
+
+To test only a subset of the servers, there are profiles with the server name. For example `-P wildfly` runs all Wildfly tests, `-P glassfish,jetty` runs all the Glassfish and Jetty tests.
+
+## Running an individual test locally
+
+To install dependencies for testing an individual module locally, run `mvn clean install -Dinstall.skip=false` in the dependency module.
+
+For example you can install all dependencies for running any individual server test module with the following command in the test root:
+```
+mvn clean install -Dinstall.skip=false -pl .,servlet-containers,servlet-containers/generic-ui,servlet-containers/generic-tests
+```
 
-Note that `mvn clean install` needs to be executed in the top-level test project or in the widget-set-testutil subproject before running tests for any individual submodule.
+This will install the parent POMs on both levels as well as the UI and server test dependencies.