shashank created CAMEL-26950:
--------------------------------

             Summary: camel-test-dst - a way to run fake worlds in modules that 
run their tests in parallel (core, jms, sjms, sql)
                 Key: CAMEL-26950
                 URL: https://issues.apache.org/jira/browse/CAMEL-26950
             Project: Camel
          Issue Type: Improvement
          Components: camel-test
            Reporter: shashank
            Assignee: shashank


The DST guide says a fake world cannot be committed in a module that runs its 
tests in parallel ({{camel.surefire.parallel=true}}). That includes camel-core 
(so the file consumer, the aggregator and the idempotent consumer), camel-jms, 
camel-sjms, camel-activemq, camel-sql, camel-jdbc and camel-quartz. Several of 
the tier 1 worlds of CAMEL-26610 (jms/sjms, file) and the repository worlds 
live there, so they are blocked today.

h3. Options
# A separate surefire execution in these modules that runs only the 
{{@DstWorld}} tests, one at a time, after the parallel ones. No new module; the 
worlds stay next to the code they test.
# A dedicated non-parallel test module per area (for example 
{{camel-test-dst-core}}) that depends on the component and holds its worlds.

Option 1 looks smaller and keeps the worlds with the component, but it changes 
the build of these modules, so it would be good to agree on the approach before 
starting. Comments welcome.

Once this is in place, the first world would be the idempotent and aggregation 
repositories with a crash and restart on the same fake (the class of 
CAMEL-26705, CAMEL-26816, CAMEL-26642).

_Filed with Claude Code on behalf of allthingssecurity._



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to