luigidemasi opened a new issue, #69: URL: https://github.com/apache/camel-kit/issues/69
> Imported from [luigidemasi/camel-kit#123](https://github.com/luigidemasi/camel-kit/issues/123), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-29. > Closed by [luigidemasi/camel-kit#124](https://github.com/luigidemasi/camel-kit/pull/124), merged on 2026-06-30. --- ## Description Camel Kit already generates Citrus integration tests for Camel routes, but the current `camel-test` flow relies mostly on static guides and the downloaded `.camel-kit/.cache/citrus/{version}/citrus-quick-reference.md`. Citrus now publishes an MCP server that exposes the Citrus test vocabulary, endpoint configurations, test action catalog, schemas, documentation, and guided test-authoring prompts. Camel Kit should integrate this MCP server so generated Citrus tests can be validated against the live Citrus catalog instead of relying only on static snippets. Published artifact: - `org.citrusframework:citrus-mcp-server:5.0.0-M2` - Maven Central: https://repo.maven.apache.org/maven2/org/citrusframework/citrus-mcp-server/5.0.0-M2/ - Citrus announcement: https://citrusframework.org/news/2026/06/18/approaching-release-5.0/ ## Expected Behavior Camel Kit should configure Citrus MCP during `camel-kit init` and make the `camel-test` skill use it during test generation. Suggested behavior: 1. Add a `citrus` MCP server to generated MCP configs for supported agents. 2. Add Citrus MCP metadata to `camel-kit-workflow.yaml`. 3. Use `org.citrusframework:citrus-mcp-server:{CITRUS_MCP_VERSION}:runner`. 4. Add distribution properties such as: - `citrus.version=5.0.0-M2` - `citrus.mcp.version=5.0.0-M2` - `citrus.mcp.repos=central=https://repo1.maven.org/maven2/` 5. Keep Citrus versioning synchronized: - MCP server version - downloaded Citrus schema/cache version - generated `jbang.properties` dependencies - `--citrus-version default` 6. Update `camel-test` guides to prefer Citrus MCP tools/resources for: - action lookup - endpoint lookup - action/endpoint schemas - YAML DSL schema validation - best-practice documentation 7. Fall back only to a same-version cached quick reference. Do not silently fall back from `5.0.0-M2` MCP to `4.9.2` schemas. 8. If neither MCP nor same-version cache is available, proceed with static examples but mark generated tests as unverified. ## Actual Behavior Camel Kit currently: - Defaults Citrus schemas to `4.9.2`. - Does not generate a Citrus MCP server config. - Uses Camel MCP for route/component analysis, but not Citrus MCP for Citrus DSL correctness. - Relies on static guide examples and cached quick-reference files for Citrus test generation. - Has some stale wording in the test persona/templates that still mentions Java Citrus test classes even though the current direction is Citrus YAML via `camel test run`. ## Additional Context Relevant files: - `camel-kit-core/src/main/resources/skills/camel-test/SKILL.md` - `camel-kit-core/src/main/resources/skills/camel-test/guides/route-analysis.md` - `camel-kit-core/src/main/resources/skills/camel-test/guides/test-generation.md` - `camel-kit-core/src/main/resources/agents/test-engineer.md` - `camel-kit-core/src/main/resources/workflow/camel-kit-workflow.yaml` - `camel-kit-core/src/main/resources/templates/mcp-configs/*.json` - `camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/generator/McpConfigGenerator.java` - `distribution.properties` Acceptance criteria: - `camel-kit init` emits a Citrus MCP server config. - Citrus MCP version and Citrus schema/cache version are resolved from a single synchronized version contract. - `camel-test` guide instructions use Citrus MCP first and same-version cache second. - Stale Java/JUnit wording in test generation persona/templates is cleaned up where it conflicts with Citrus YAML generation. - Tests cover generated MCP config allowlists and version/template rendering. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
