Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
From: nicolaferraro <git@git.apache.org>
To: dev@camel.apache.org
Reply-To: dev@camel.apache.org
Message-ID: <git-pr-1036-camel@git.apache.org>
Subject: [GitHub] camel pull request #1036: CAMEL-10052: Spring-boot integration tests
Content-Type: text/plain
Date: Wed, 15 Jun 2016 12:48:01 +0000 (UTC)
archived-at: Wed, 15 Jun 2016 12:48:03 -0000

GitHub user nicolaferraro opened a pull request:

    https://github.com/apache/camel/pull/1036

    CAMEL-10052: Spring-boot integration tests

    I created an integration test module that checks the compatibility of every component with spring-boot. For each component, it assembles a spring-boot jar and start checking the component. I've collected some small issues by running all tests with the current modules (I'll open Jiras).
    
    This is an excerpt fro the provided readme:
    
    The camel-itest-spring-boot module provides an integration testing framework for camel components, to check their compatibility with spring-boot.
    
    Each test-case defined in `src/test/java/org/apache/camel/itest/springboot` executes the following steps:
    - Creates a spring-boot jar by putting the spring-boot loader, test classes and some utility classes in the main jar,
    and all other libraries (including the camel component under test) as nested jars;
    - Launches a new JVM with the spring-boot jar in the classpath, then starts the spring-boot platform;
    - Executes a list of predefined checks in the spring-boot environment to verify that the component has been created correctly:
    checks that the camel context has been created, that the camel components can be activated (including data format and languages).
    
    **Additional options**
    
    Test options can be changed from the `src/test/resources/spring-boot-itest.properties` file.
    
    Some useful options include:
    - **includeTestDependencies (default=false)**: when this option is enabled,
    the integration test will locate the module `pom.xml` file and include in the spring-boot jar also the test-scoped dependencies of the module.
      The inclusion of other libraries often activates some hidden behaviour of spring-boot.
      *Note: logging libraries (eg. `log4j`) included in test scope are ignored, to prevent conflict with spring-boot logging system.*
    - **unitTestEnabled (default=false)**: when this option is enabled,
    the integration test will locate the test-classes of the module and run the unit tests after the execution of the usual checks.
      *Note: a full build of each component is required prior to running the unit tests. Test dependencies are implicitly included.*
    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nicolaferraro/camel CAMEL-10052

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1036.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1036
    
----
commit 4bad78bc9f6679cd86315f915668cd948e755797
Author: Nicola Ferraro <ni.ferraro@gmail.com>
Date:   2016-06-15T12:43:03Z

    CAMEL-10052: Spring-boot integration tests

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---