Claus Ibsen created CAMEL-26724:
-----------------------------------
Summary: camel-chaos - assertions for chaos in a test: the
verdict, an expectation, and how often a rule fired
Key: CAMEL-26724
URL: https://issues.apache.org/jira/browse/CAMEL-26724
Project: Camel
Issue Type: New Feature
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.24.0
W-3 of the stage 2 decisions on CAMEL-26607: a finding from a hands-on chaos
session becomes a regression test.
* {{ChaosAssertions}} in camel-chaos: {{assertVerdict(context, PASS, timeout)}}
waits until the report is final and checks the verdict;
{{assertExpectationMet(context, ruleId, timeout)}}; {{assertFired(context,
ruleId, atLeast)}}; {{awaitFinalReport(context, timeout)}}. A failure says why,
with the report.
* No dependency on JUnit or camel-test: the assertions throw
{{AssertionError}}, and chaos is switched on in a test with
{{camel.chaos.enabled=true}}, {{camel.chaos.seed}} and {{camel.chaos.rules}} or
{{camel.chaos.scenario}}, or rules added with {{ChaosManager}}.
* The documentation has a test with {{CamelTestSupport}}.
Not here: a Citrus action for {{camel test run}} (it belongs in Citrus); a
JUnit annotation for the rules (camel-test would depend on camel-chaos).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
