Claus Ibsen created CAMEL-26495:
-----------------------------------
Summary: camel-jbang - camel run and the camel_run tool do not
start a Citrus test, and point to camel test run
Key: CAMEL-26495
URL: https://issues.apache.org/jira/browse/CAMEL-26495
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.24.0
A Citrus test of a Camel project, such as {{test/orders.citrus.it.yaml}}, runs
with {{camel test run}}. In the local-model benchmark, the model gave the test
to the camel_run tool of the camel-jbang-mcp server, and Camel started it as an
integration with no routes. {{camel run test/orders.citrus.it.yaml}} did the
same.
The CLI and the AI tools now point to the {{camel test}} commands for Citrus:
* {{camel run}} (also {{camel dev}} and {{camel debug}}) with only Citrus tests
exits with 2: "test/orders.citrus.it.yaml is a Citrus test, not a route: run it
with camel test run test/orders.citrus.it.yaml". The same goes for a folder
that holds only Citrus tests ({{camel run test/}}).
* Citrus tests given with routes, such as by {{camel run *}}, are skipped with
one line each, and the routes run as before. A directory or {{--source-dir}}
with a test folder runs as before.
* The camel_run tool starts nothing for Citrus tests only. With routes, it
starts the routes, and its answer lists the tests it skipped and how to run
them.
* The camel run help, the MCP server instructions, and the Testing Plugin,
running and MCP docs pages say {{camel test init}} and {{camel test run}}. The
Testing Plugin page used a file name that {{camel test run}} skips in Citrus 5.
* The 4.24 upgrade guide describes the new exit code.
_Filed by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
