Croway commented on PR #2083:
URL:
https://github.com/apache/camel-spring-boot/pull/2083#issuecomment-6745368515
Thanks for the starter! Please also add the integration test
`tests/camel-itest-spring-boot/src/test/java/org/apache/camel/itest/springboot/CamelVertxMqttIT.java`:
```java
package org.apache.camel.itest.springboot;
import
org.apache.camel.itest.springboot.common.AbstractSpringBootBaseTestSupport;
import org.junit.jupiter.api.Test;
public class CamelVertxMqttIT extends AbstractSpringBootBaseTestSupport {
@Test
void componentTest() {
assertComponent(inferComponentName(getClass()));
}
}
```
This command generates it with the license header: `cd
tests/camel-itest-spring-boot && mvn -Pgenerate -Dstarter=vertx-mqtt`
**Why:** `CamelCatalogIT` requires a `Camel<ArtifactId>IT` for every catalog
component that has a starter. Now that `vertx-mqtt` is in the 4.24.0-SNAPSHOT
catalog, it fails with `Missing component integration tests:
camel-vertx-mqtt-starter (vertx-mqtt)`. PR CI only runs the tests module when a
file in it changes, so this PR stays green and the failure would show up on the
next Daily build. With the IT added, PR CI runs `CamelCatalogIT` and
`CamelVertxMqttIT`, which starts an app generated from the archetype and
resolves the component. Both pass locally with the IT added.
_Claude Code (Opus 5.5) on behalf of Federico Mariani_
--
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]
