Croway commented on PR #1547:
URL:
https://github.com/apache/camel-spring-boot/pull/1547#issuecomment-3441727413
Sure @squakez
`Just for my understanding, are those new tests calling the related unit
test in the core` yes and no:
* componentTest:
- Looks up the component in the Spring Boot CamelContext
- Verifies the component can be retrieved successfully (not null)
- Validates that the component is properly registered and accessible
* dataformatTest:
- Attempts to resolve the data format from the CamelContext
- Verifies the data format can be retrieved successfully (not null)
- Validates that the data format is properly registered
Same for the language.
the `runModuleUnitTestsIfEnabled` execute tests in the camel spring boot
component, but I think we updated those tests to use the SpringBoot testing
best practices and Camel ones.
Overall the Camel Spring Boot itests are handy because they check potential
issues with dependency alignments, in particular, Spring Boot may use
dependencies version that differ from the Camel one, and from time to time we
need to add overrides or refactor some stuff so that the component can work on
Camel and Camel Spring Boot. For example
https://github.com/apache/camel-spring-boot/pull/1545 the drill component was
preventing Camel Spring Boot to start because the `-all` dependency was
introducing reeeeeeeally old jackson versions that are not compatible with
Spring Boot.
These tests are slow, 30 minutes on my laptop, but really useful.
The overall idea is that Camel tests the component itself, then, Camel
Spring Boot tests if the component can be installed successfully, given that
the component is successfully tested in Camel, and the component starts
successfully on Camel Spring Boot, then, the tests should be successfully on
Camel Spring Boot too.
There are some special components like platform-http that differs, but this
logic should be applicable for most of the components.
--
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]
