orpiske opened a new pull request #4081:
URL: https://github.com/apache/camel/pull/4081


   This is a proposed solution for CAMEL-12336. It reworks the tests in 
camel-itests so that: 
   
   - we can reduce the time required to launch every test case by enabling fork 
reuse
   - we can reuse test infrastructure resources per test and reduce their 
execution time
   
   Details for the test duration improvents are provided on the ticket, but in 
general it seems 
   provide roughly 50% improvement in test duration (ie.: test decreases from 
7:40 min to 3:30 min
   on my desktop) obversable in different setups. 
   
   The surefire-plugin behavior now defaults to reusing threads, however 
options are provided so 
   that the previous behavior can be enabled for further verification. This can 
be adjusted via a
   property `camel.itest.fork.reuse` that can be passed to maven. For example, 
to return to the old
   behavior, one can run:
   
   ```mvn -Dcamel.itest.fork.reuse=false verify```
   
   One additional parameter for setting the fork count is provided 
`camel.itest.fork.count` for more
   flexibility but it continues to use the previous default value of 1. The 
benefits of this flag are
   only minor at this moment. 
   
   Known issues: none (apparently), however a bug in the surefire plugin causes 
the reporting of the
   test number to be miscalulated: 
https://issues.apache.org/jira/browse/SUREFIRE-1643. This does not 
   seem to affect the stability of the tests in any of the scenarios/setups I 
tested.
   
   
   [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change 
(usually before you start working on it).  Trivial changes like typos do not 
require a JIRA issue.  Your pull request should address just this issue, 
without pulling in other changes.
   [x] Each commit in the pull request should have a meaningful subject line 
and body.
   [x] If you're unsure, you can format the pull request title like 
`[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` 
with the appropriate JIRA issue.
   [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   [x] Run `mvn clean install -Psourcecheck` in your module with source check 
enabled to make sure basic checks pass and there are no checkstyle violations. 
A more thorough check will be performed on your pull request automatically.
   Below are the contribution guidelines:
   https://github.com/apache/camel/blob/master/CONTRIBUTING.md


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to