davsclaus opened a new issue, #3288:
URL: https://github.com/apache/camel-kamelets/issues/3288
A follow-up of #3261. 200 of the 221 Kamelets now have a Citrus test. While
writing them, we found Kamelet tests that are disabled, weak or flaky. Each
item can be done on its own.
### Disabled tests
These Kamelets have only a disabled test, so they can't be labelled
`camel.apache.org/kamelet.verified` (see #3287).
- [ ] `redis-sink` (`redis/redis-sink-route.citrus.it.yaml.disabled`): it
reads `${CITRUS_TESTCONTAINERS_REDIS_SERVICE_PORT}`, which Citrus 5.2 never
sets; the generic container exposes `CITRUS_TESTCONTAINERS_<NAME>_PORT`. That's
the likely cause of its flakiness. Fix the variable and enable it.
- [ ] `mqtt5-sink`, `mqtt5-source`
(`mqtt5/mqtt5-sink-to-source-route.citrus.it.yaml.disabled`): disabled since
#2925.
- [ ] `nats-sink`, `nats-source`
(`nats/nats-sink-to-source-route.citrus.it.yaml.disabled`): disabled since
#2925.
- [ ] `cassandra-sink`
(`cassandra/cassandra-sink-route.citrus.it.yaml.disabled`).
- [ ] `salesforce-create-sink`, `salesforce-update-sink`,
`salesforce-delete-sink`: only the old `salesforce-sink.feature` and Pipe
files, which are not run. A test needs a stand-in for the Salesforce login and
REST API, as `salesforce-composite-upsert-sink-route` has.
### Weak tests
- [ ] `mongodb-sink`, `mongodb-source` and `postgresql-source`: they only
check log lines written before the Kamelet or outside it, not what the Kamelet
wrote or gave. They should read back from the database or check the body the
Kamelet gives.
- [ ] `azure-functions-sink`: no test that the incoming `Authorization`
header is not sent on to the function. Citrus can't assert that a header is
missing, so this needs another way, for example echoing the received headers
into the body.
### Flaky tests and fixed ports
- [ ] The Couchbase tests bind the fixed host ports 8091, 8093 and 11210, so
they fail when another process uses them.
- [ ] `SlackIT` can fail with a port-bind race (seen on 2026-11-18).
- [ ] `ftps-source-route-test` fails often in CI, and reruns sometimes pass.
The integration connects but never delivers. #3284 prints the integration log
on failure, to find the cause.
_Claude Code on behalf of Claus Ibsen_
--
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]