Version 8
Created by takis on Nov 24, 2016 10:44 AM. Last modified by takis on Jan 6, 2017 5:36 AM.

    The JBoss testsuite to develop tests against infinite number of JBoss Servers.

    An additional JBoss testsuite in order to facilitate QE.

    Write your tests once and run them against any version of EAP and Wildfly application servers.

     

    EAP-WILDFLY ADDITIONAL TESTSUITE VERSIONS.jpg

     

     

    ADVANTAGES of EAT :

     

    - Writing the tests once and testing against infinite number of Application Servers.

    - Having all the tests at one place.

    - Comparison of the servers based on the testsuite.

    - Guarding against regression.

    - Faster convergence among the servers.

    - Comparison of the servers based on tests of the past and the present.

    -Addition of tests with possible future features that are not at the moment available.

    -It makes possible to push a testcase of a fix regarding a specific component of the server, without the component version to have been updated at the server pom.

     

     

     

    OTHER FEATURES :

     

    - Infinite number of servers could be added in Eap-Additional-Testsuite, while the tests included could be tested against all these servers.

    - Eap-Additional-Testsuite could be a very helpful tool in combination with the documentation. In parallel with the documentation, examples of use cases could be provided, which could be tested against all the servers.

    - Eap-Additional-Testsuite is the first component to change the relation of Component -> Server to Component <-> Server, as this component can be considered as a part of a Server, but also a Server can be considered as a part of Eap-Additional-Testsuite.

     

     

    HOW TO USE :

     

    In order to run a test in Wildfly Server :

     

      1. Make sure that JBOSS_FOLDER environment variable is set with the path to your WILDFLY Server directory.

      2. Make sure that JBOSS_VERSION environment variable is set with the version of WILDFLY Server.

      3. Make sure that LOCAL_REPO_DIR environment variable is set with the path to your local maven repo.

      4. Build and run the additional testsuite activating the WILDFLY profile (-Dwildfly) and using the standalone mode (-Dstandalone) : mvn clean install -Dwildfly -Dstandalone -Dmaven.repo.local=${local.maven.repo}

     

    Note : In order to run EAT the equivalent server produced artifacts should be included in your maven local repository.

     

     

    Github Repo : GitHub - jboss-set/eap-additional-testsuite: An additional JBOSS EAP-WILDFLY testsuite in order to facilitate QE