Usage

  • Based on TestContainers and uses Docker to execute the tests under various Databases, Servlet Engines and Browsers.
  • The only requirements for running these tests is to have Docker installed locally and to have the user under which you run your IDE and the Maven build be able to use the docker executable.
  • Tests get injected XWikiWebDriver and TestUtils instances as test method parameters.
  • Test results is recording in a FLV file in the target directory.
  • A screenshot of the UI when the test is failing is also taken in the target directory.
  • When test execute it's possible to connect to the running VNC server and see the UI by using a VNC client and connect to the VNC URL printed in the console, e.g. vnc://vnc:[email protected]:32936.
  • The version for the platform dependencies is specified using the platform.version property in the pom.xml file executing the tests.
  • The test configuration options can be accessed from tests by specifying a method parameter of type TestConfiguration (see examples below).
    • You can get access to the IP address/port to use to connect to XWiki from the host machine: testConfiguration.getServletEngine().getIP()/getPort()
    • You can get access to the IP address to use to connect to the host machine from inside XWiki: testConfiguration.getServletEngine().getHostIP()
    • You can get access to the IP address/port used internally by XWiki (for example to generate URLs): testConfiguration.getServletEngine().getInternalIP()/getInternalPort()

Configurations options

Note:

  • When passing as Java annotation attributes, in functional tests, the format is @UITest(<Option Name> = <Value>)
  • When passing the options as System Properties, the format is -Dxwiki.test.ui.<Option Name>=<Value>
    • Except for passing properties where the format is -Dxwiki.test.ui.properties.<Property name>=<Property Value>
    • Except for extraJARs, sshPorts & forbiddenServletEngines which cannot be set from System Properties.
    • Except for passing databaseCommands where the format is -Dxwiki.test.ui.database.commands.<Command name>=<Command Value>
  • System properties have priority over Java annotation attributes
  • The xwiki.test.ui.dependencies configuration value can only be passed as a system property.
Option NameDefault ValueValid ValuesDescription
browserfirefox
  • firefox (Browser.FIREFOX)
  • chrome (Browser.CHROME)
The browser used in the tests. Note that the version of the browser used is controlled by the version of Selenium that is defined in the pom.xml of xwiki-platform-test-docker.
databasehsqldb_embedded
  • mysql (Database.MYSQL)
  • postgresql (Database.POSTGRESQL)
  • hsqldb_embedded (Database.HSQLDB_EMBEDDED)
  • oracle DB (Database.ORACLE)
The database used in the tests. Available tags are those listed on the Dockerhub page for the database image used. Note: for Oracle, we only have Oracle 11g Release 2.
servletEnginejetty_standalone
  • tomcat (ServletEngine.TOMCAT)
  • jetty (ServletEngine.JETTY)
  • jetty_standalone (ServletEngine.JETTY_STANDALONE)
  • external (ServletEngine.EXTERNAL)
The Servlet Engine used in the tests. Use external to use your own started and alreayd provisioned XWiki instance.
verbosefalse
  • true
  • false
When active, displays more logs in the console (especially container startup logs)
debugfalse
  • true
  • false
When active, displays debug logs in the console (trace levels for Test Containers). Also starts XWiki in debug mode when using the "Jetty Standalone" Servlet Engine (and starts it with suspend on, i.e. wait for the remote debugger to connect to it before progressing, to make it easy to debug XWiki's server side).
saveDatabaseDatafalse
  • true
  • false
By default, database data is not saved between test executions. Note that if you decide to save database data, they'll be saved under a docker user by Docker and you need your local user to be able to remove them if you want to clean your Maven target directory.
offlinefalse
  • true
  • false
When offline, the custom XWiki WAR generation and the XWiki provisioning are done solely from your local Maven repository. Otherwise, when artifacts are not present locally or newer SNAPSHOT versions are available, they'll be fetched from Maven remote repositories. Moreover no docker pull check is performed in offline mode.
databaseTagLatest supported version by XWikiAny Docker tag available from Dockerhub for the container imageVersion of the database to use. Isn't supported for HSQLDB Embedded since it doesn't run in a Docker container.
servletEngineTagLatest supported version by XWikiAny Docker tag available from Dockerhub for the container imageVersion of the Servlet Engine to use. Isn't supported for Jetty Standalone since it doesn't run in a Docker container.
jdbcDriverVersionLatest version validated by the XWiki dev teamAny version for the specified database that is available on Maven Central, e.g. for MySQL the groupId/artifactId is mysql/mysql-connector-java. 
vnctrue
  • true
  • false
When active a VNC container is started to record a video of the tests and more generally to allow connecting to the UI running the tests. Useful when debugging.
propertiesNo default (empty)Check the *.vm files for the configuration files to see the list of possible values.Velocity properties that are applied when generating XWiki's configuration files: xwiki.cfg, xwiki.properties and hibernate.cfg.xml. Example: Tell XWiki that minification is off: -Dxwiki.test.ui.properties.xwikiPropertiesAdditionalProperties=debug.minify=false or @UITest(properties = { "xwikiPropertiesAdditionalProperties=debug.minify=false" }). Note that the xwikiCfgPlugins property will be merged with the default values unless you start the new property value with the ^ character.
extraJARsNo default (empty)Comma-separated list of <groupId>:<artifactId>There are cases where the module being tested cannot be fully deployed as an extension into a running XWiki and it needs to deploy one or several JARs into WEB-INF/lib. One such example is when an extension includes a Hibernate HBM file, as right now only HBM files located in JARs in WEB-INF/lib are supported.
sshPortsNo default (empty)List of integersThe list of ports that should be SSH-forwarded when connecting from a Docker container to the host (i.e. when using the host.testcontainers.internal. This is in addition to port 8080 which is always added. For example if you need XWiki to send a mail to a SMTP server running on port 3025 on the host, you should add port 3025 to the list.
profilesNo default (empty)Comma-separated list of Maven profile idsWhen specified the defined profiles are active when resolving dependencies from the current POM.
forbiddenServletEnginesNo default (empty)List of ServletEngines enumsList of Servlet Engines for which the tests will be skipped (usually because they'd fail on them).
databasePropertiesNo default (empty)See Docker documentation for the target imageList of database docker commands to use and that will override default commands (example of command character-set-server=utf8mb4 which will translate into --character-set-server=utf8mb4 at runtime).
dependenciesNo default (empty)Comma-separated list of Maven coordinatesList aritfacts that will be provisioned in the running XWiki instance. When specified then current pom.xml dependencies are not used to find out what to provision. This can be used for example in cases when you don't want to use project dependencies in order to not draw older version of dependencies (such as when you need to run functional docker-based tests in a specific more recent vesion of XWiki than the one used to build the code). Accepted format is groupId:artifactId, groupId:artifactId:version and groupId:artifactId:type:version. Since 11.2RC1.

Examples

Full Examples

Example 1: Basic test

@UITest
public class SeleniumTest
{
   @Test
   public void test(XWikiWebDriver driver, TestUtils setup)
   {
        driver.get("http://xwiki.org");
        assertThat(driver.getTitle(),
            containsString("XWiki - The Advanced Open Source Enterprise and Application Wiki"));
        driver.findElement(By.linkText("XWiki's concept")).click();
   }
}

Example 2: Choosing Container + DB + Browser and versions

@UITest(database = Database.MYSQL, databaseTag = "5", servletEngine = ServletEngine.TOMCAT, servletEngineTag = "8",
  browser = Browser.CHROME)
public class MenuIT
...
@UITest(database = Database.POSTGRESQL, databaseTag = "9", servletEngine = ServletEngine.JETTY,
  servletEngineTag = "9", browser = Browser.CHROME)
public class MenuIT
...
@UITest(database = Database.HSQLDB_EMBEDDED, servletEngine = ServletEngine.JETTY_STANDALONE,
  browser = Browser.FIREFOX)
public class MenuIT
...

Example 3: Test using Greenmail + Hibernate HBM

@UITest(sshPorts = {
       3025
   },
    properties = {
       "xwikiDbHbmCommonExtraMappings=mailsender.hbm.xml",
       // Pages created in the tests need to have PR since we ask for PR to send mails so we need to exclude them from
       // the PR checker.
       "xwikiPropertiesAdditionalProperties=test.prchecker.excludePattern=.*:MailIT\\..*"
   },
    extraJARs = {
       "org.xwiki.platform:xwiki-platform-mail-send-storage"
   }
)
public class MailIT
...

Example 4: Passing Test Configuration

@Test
public void verifyMail(TestUtils setup, XWikiWebDriver webDriver, TestConfiguration testConfiguration)
   throws Exception
{
   ....
}

Example 5: Specifying explictly dependencies

Example of deploying a 1.10-SNAPSHOT version of org.xwiki.contrib.latex:latex-export (and its dependencies) into a 11.2-SNAPSHOT version of XWiki. In this example the POM of org.xwiki.contrib.latex:latex-export depends on XWiki 10.2. Thus this example demonstrates running the tests in a more recent version of XWiki than the code was built on.

...
<parent>
 <groupId>org.xwiki.platform</groupId>
 <artifactId>xwiki-platform</artifactId>
 <version>11.2-SNAPSHOT</version>
</parent>
<groupId>org.xwiki.contrib.latex</groupId>
<artifactId>latex-test</artifactId>
<version>1.10-SNAPSHOT</version>
...
<plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-failsafe-plugin</artifactId>
 <configuration>
   <includes>
     <include>**/AllIT.java</include>
   </includes>
   <systemProperties>
     <xwiki.test.ui.dependencies>org.xwiki.contrib.latex:latex-export</xwiki.test.ui.dependencies>
   </systemProperties>
 </configuration>
</plugin>

Best Practices

Scenarios

Always use scenarios and use JUnit5's @Order(...) annotation. For example:

@UITest
public class MenuIT
{
    @Test
    @Order(1)
    public void verifyMenuInApplicationsIndex(TestUtils setup)
    {
      ...
    }

    @Test
    @Order(2)
    public void verifyMenuCreationInLeftPanelWithCurrentWikiVisibility(TestUtils setup)
    {
      ...
    }

    @Test
    @Order(3)
    public void verifyMenuIsAvailableInAdministration(TestUtils setup) throws Exception
    {
    ...
  }
}

Suites

Use JUnit5's @Nested annotation. For example:

@UITest(...)
public class AllIT
{
    @Nested
    @DisplayName("Office Import Tests")
    class NestedOfficeImporterIT extends OfficeImporterIT
    {
    }

    @Nested
    @DisplayName("Office Export Tests")
    class NestedOfficeExportIT extends OfficeExportIT
    {
    }
}

Test Reference

A lot of tests need to create a wiki page for testing. Example to do this:

@Test
public void showAndHideEditComments(TestUtils setup, TestReference reference) throws Exception
{
        ViewPage vp = setup.gotoPage(reference);
...

More generic way (more verbose but can useful in some cases) using JUnit5's TestInfo class:

public class MailIT
{
   private String testClassName;

   @BeforeEach
   public void setUp(TestInfo info)
   {
       this.testClassName = info.getTestClass().get().getSimpleName();
   }
 ...
}

Docker out of Docker

The XWiki's CI is using a Jenkins Agent Docker image to execute the job builds. Thus, the Docker-based functional tests spawn Docker containers (using TestContainers) that execute inside Docker. This is the pattern called DOOD (Docker out of Docker). See TC's best practice about this.

There are some consequences when writing tests for XWiki:

  • Never use volume mapping or it won't execute fine. This is because that would require the Jenkins Agent Docker container to have that volume mapping defined too and the mapping would need to use the exact host path and container path. So, in short, it won't work. Instead copy files that you need to have in the container. Adn copy file out if need be. Here's an example from the LaTeX extension on how to achieve this:
    try (GenericContainer container = new GenericContainer("blang/latex:ubuntu")) {
       // Note: we copy files instead of mounting volumes so that this can work when using DOOD
       // (Docker out of Docker).
       MountableFile mountableDirectory = MountableFile.forHostPath("target/latex");
        container.withCopyFileToContainer(mountableDirectory, "/data");

        container.withCommand("/bin/sh", "-c", "sleep infinity");
        container.withLogConsumer(new Slf4jLogConsumer(LOGGER));
        container.start();
        Container.ExecResult result = container.execInContainer("pdflatex", "-shell-escape", "index.tex");
        String stdout = result.getStdout();
        LOGGER.info(stdout);
        assertTrue(stdout.contains("Output written on index.pdf"));

        container.copyFileFromContainer("/data/index.pdf", "target/latex/index.pdf");
    }

Test Resources

You might need test resources to be used in interaction with the wiki (e.g. to upload an attachment). Any test resources placed in src/test/resources is made automatically available to the browser container by mounting the dedicated volume mapped to target/test-classes. Then, in your test, you can use the dedicated method to get access to the files located in target/test-classes.

For example:

String resourceDirPath = testConfiguration.getBrowser().getTestResourcesPath();
File myResourceFile = new File(resourceDirPath, filename);

Test Coverage

Activate support for Clover by setting the xwiki.test.ui.profiles property in the clover profile in the pom.xml file for the test.

Example:

 <profiles>
   <profile>
     <id>clover</id>
     <!-- Add the Clover JAR to the WAR so that it's available at runtime when XWiki executes.
           It's needed because instrumented jars in the WAR will call Clover APIs at runtime when they execute. -->

     <dependencies>
       <dependency>
         <groupId>org.openclover</groupId>
         <artifactId>clover</artifactId>
       </dependency>
     </dependencies>
     <build>
       <plugins>
         <plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-failsafe-plugin</artifactId>
           <configuration>
             <systemProperties combine.children="append">
               <!-- Tell the Docker-based test to activate the Clover profile so that the Clover JAR is added to
                     WEB-INF/lib -->

               <property>
                 <name>xwiki.test.ui.profiles</name>
                 <value>clover</value>
               </property>
             </systemProperties>
           </configuration>
         </plugin>
...

Existing XWiki instance

If you want to avoid the Docker-based tests to start and stop XWiki every time you re-run the tests (for example when you're developping/debugging something), you can tell the Docker Test framework to not provision an XWiki instance and to use your XWiki instance instead.

This is achieved by specifying @UITest(servletEngine = ServletEngine.EXTERNAL) or passing the xwiki.test.ui.servletEngine=external system property.

A common use case is to debug a failing test. Here's what you can do:

## Run the test once to see if it fails and to generate the XWiki instance. This may take some time.
> mvn clean install -Dtest=NavigationPanelIT
## Open a new console, look for the generated XWiki instance inside the target folder and start it.
../target/../jetty > start_xwiki.sh
## Modify the test as needed then go back to the initial console and compile the tests.
## Note that you may also need to build the page objects module if you change those too.
> mvn compiler:testCompile
## Then run the test again to see the changes. This should be way faster than the initial test run.
> mvn surefire:test -Dxwiki.test.ui.servletEngine=external -Dtest=NavigationPanelIT

Architecture

xwiki-testcontainers.png
See Vincent's blog for more details

CI Jobs

There are 3 CI jobs executing Docker-based functional tests:

  • Job 1: run all tests on latest versions of supported configs.
  • Job 2: run smoke tests (ie a few tests only) on all supported configs.
  • Job 3: run smoke tests on unsupported configs (MySQL 8.x, Tomcat 9.x, etc) that we want to support in the future.

Configuration definitions and job sources are all here.

Tags:
Created by Vincent Massol on 2018/11/25 16:20
   

Get Connected