oscerd opened a new pull request, #2905: URL: https://github.com/apache/camel-kamelets/pull/2905
## Summary The **Testing** section of the developer guide (`docs/modules/ROOT/pages/development.adoc`) documented **YAKS + Gherkin `.feature` files run against a Kubernetes cluster** — but the repository's tests are **Citrus** tests under `tests/camel-kamelets-itest/` that drive Kamelets with **Camel JBang**. A new contributor following the guide today writes tests that don't fit the project's CI. This rewrites the section to describe the actual workflow: - a `Pipe` that wires the Kamelet under test; - a `*.citrus.it.yaml` test that runs the `Pipe` via `camel jbang run` and asserts the result via `camel jbang verify` (`logMessage`) or the Citrus HTTP server; - a `*IT.java` `@CitrusTestFactory` that registers the resource folder; - how to test a source vs a sink, and how to run the suite (`mvn verify -pl :camel-kamelets-itest -Denable.integration.tests`, or a single factory with `-Dit.test=CommonIT#<name>`). All examples use real, merged suites (`log`, `timer`, `CommonIT`), and the doc reiterates that a passing behaviour test justifies the `camel.apache.org/kamelet.verified: "true"` label. ## Verification - AsciiDoc structure checked (balanced source blocks, valid section hierarchy); no YAKS/Gherkin/`.feature` references remain in the section. Antora rendering is validated by the `pr-doc-validation` workflow. --- _AI-generated by Claude Code on behalf of Andrea Cosentino (@oscerd)._ -- 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]
