[jira] [Resolved] (CAMEL-3960) camel-test - Add support for creating CamelContext once per class, to re-use it when having multiple test methods

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3960.
--------------------------------

    Resolution: Fixed

Added this for camel-testng as well

> camel-test - Add support for creating CamelContext once per class, to re-use it when having multiple test methods
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3960
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3960
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-test
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>
> As Oleg posted on my blog
> http://davsclaus.blogspot.com/2011/05/faster-unit-testing-apache-camel-source.html
> We should add an option so end users can enable per class CamelContext (its shared). This ensure there is less overhead creating/shutting down CamelContext between test methods. 
> Then they can decide to enable this in case their test can leverage this feature. This will speedup unit testing.
> This requires JUnit4 and its support for @BeforeClass and @AfterClass
> We should look into adding the same support for TestNG as well.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira