[
https://issues.apache.org/jira/browse/CAMEL-26876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26876.
---------------------------------
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/29698
> camel-jbang - AI tools: a Citrus test that verifies a log line with regex
> escapes is refused with the line to write
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26876
> URL: https://issues.apache.org/jira/browse/CAMEL-26876
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Follow-up from the local-model benchmark (qwen3.6, r32), test-citrus-orders
> step 1. In 3 of 7 runs the model wrote
> {code}
> - camel:
> cli:
> verify:
> integration: orders
> logMessage: "Order ORD-1001 accepted for C-482 with 2 line\\(s\\)"
> {code}
> Citrus checks that the integration logged a line that contains the logMessage
> as written, so the backslashes made the test fail ("has not printed message
> ... after 60 attempts"). The model had first written the check as a regular
> expression (assert-log: pattern:), which is not a Citrus action, and kept the
> escapes when it moved the text to logMessage.
> * A logMessage with a backslash before one of ( ) [ ] { } . * + ? ^ $ | is
> now refused: the message says that logMessage is plain text, and ends with
> the line to write, without those backslashes.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
