Claus Ibsen created CAMEL-26493:
-----------------------------------
Summary: camel-jbang - AI tools: a Citrus test is checked as YAML,
not as a route, and the examples show their Citrus tests
Key: CAMEL-26493
URL: https://issues.apache.org/jira/browse/CAMEL-26493
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.24.0
Two gaps found by the new Citrus example of the local-model benchmark
(test-citrus-orders: the model writes a Citrus YAML test and runs it with camel
test run).
*A Citrus test was refused as a Camel route*
camel_write_file, camel_edit_file and camel_validate_source validated every
.yaml file against the Camel YAML DSL. A new test/orders.citrus.it.yaml was
refused with errors such as "a Camel YAML file is a list of entries", and those
errors led the model to write Camel routes into the test. A Citrus test file
(*.citrus.yaml, *.citrus.it.yaml, *.citrus.*.yaml) is now checked as YAML only:
a parse error refuses the write with its line and column. It gets no Camel
repairs, route notes or reload, and the answer says to run it with camel test
run.
*No Citrus test to learn from*
camel_catalog_examples found nothing for "citrus", and the file lists of the
examples left out test/, so the model could not fetch a sample test, although
most examples have one. The bundled examples now include their
test/<name>.citrus.it.yaml (27 files, from camel-jbang-examples), the file list
shows it, camel_catalog_example_file returns it, and a filter of "citrus" finds
the examples with a Citrus test. The filter now matches every word in any
order, instead of the whole text as one substring.
_Filed by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
