[
https://issues.apache.org/jira/browse/CAMEL-26814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-26814:
--------------------------------
Description:
The run options form (F2 > Run an example..., Run from folder..., and running a
Maven project) can now turn on chaos with a *Chaos testing* checkbox, which
adds {{camel run --chaos}}. An example or a project often comes with test files
of its own that the form does not offer yet:
h3. Chaos scenario
When the example or folder has chaos scenarios in {{test/chaos/*.chaos}} (see
CAMEL-26722, CAMEL-26761), the form offers them next to the checkbox: none, or
one of the scenarios, which is passed as {{--chaos=test/chaos/<name>.chaos}} so
its rules are added at startup. As with the checkbox, nothing is passed with
profile prod, where camel-chaos stays off.
The Citrus tests part moved to CAMEL-26849 (4.25.0).
_Claude Code on behalf of davsclaus_
was:
The run options form (F2 > Run an example..., Run from folder..., and running a
Maven project) can now turn on chaos with a *Chaos testing* checkbox, which
adds {{camel run --chaos}}. An example or a project often comes with test files
of its own that the form does not offer yet:
h3. Chaos scenario
When the example or folder has chaos scenarios in {{test/chaos/*.chaos}} (see
CAMEL-26722, CAMEL-26761), the form offers them next to the checkbox: none, or
one of the scenarios, which is passed as {{--chaos=test/chaos/<name>.chaos}} so
its rules are added at startup. As with the checkbox, nothing is passed with
profile prod, where camel-chaos stays off.
h3. Citrus tests
The example browser already marks the examples with Citrus tests
({{test/*.citrus.it.yaml}}). The form could offer to run one of them with
{{camel test run <file>}}. Note that such a test starts the integration itself
(its {{camel: cli: run:}} action) and then verifies it, so this is a different
way of launching rather than an extra option of {{camel run}}:
* choose between running the example and running one of its Citrus tests (or
all of them)
* show the test outcome (pass or fail, and the failing action) when it ends,
and keep its log, as for a run
* the integration the test starts should show up and be selected as usual, so
the tabs can be used while the test runs
* decide which of the run options still apply to a test (runtime, profile,
port, chaos ...), and grey out the rest
Possibly the two meet: a Citrus test run with chaos on, to check the example
holds up under faults.
_Claude Code on behalf of davsclaus_
Summary: camel-jbang - run options form: pick a chaos scenario of an
example or folder (was: camel-jbang - run options form: pick a chaos scenario,
and run the Citrus tests of an example or folder)
> camel-jbang - run options form: pick a chaos scenario of an example or folder
> -----------------------------------------------------------------------------
>
> Key: CAMEL-26814
> URL: https://issues.apache.org/jira/browse/CAMEL-26814
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> The run options form (F2 > Run an example..., Run from folder..., and running
> a Maven project) can now turn on chaos with a *Chaos testing* checkbox, which
> adds {{camel run --chaos}}. An example or a project often comes with test
> files of its own that the form does not offer yet:
> h3. Chaos scenario
> When the example or folder has chaos scenarios in {{test/chaos/*.chaos}} (see
> CAMEL-26722, CAMEL-26761), the form offers them next to the checkbox: none,
> or one of the scenarios, which is passed as
> {{--chaos=test/chaos/<name>.chaos}} so its rules are added at startup. As
> with the checkbox, nothing is passed with profile prod, where camel-chaos
> stays off.
> The Citrus tests part moved to CAMEL-26849 (4.25.0).
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
