Details
-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
camel-k-1.8.1
-
None
-
Kamelet continuous upstream testing
-
False
-
None
-
False
-
To Do
-
100
-
100%
-
100
-
100%
-
Todo
Description
- Why?
- Get early feedback from Kamelet catalog & quickstarts
- Increase test coverage for non-functional requirements (e.g. configuration via secrets, configmaps, properties)
- Errors are considered as blockers for a release
- Test against nightly Camel K snapshot
- Test against LTS versions of Camel K 1.9.x, 1.8.x, 1.6.x?
- GitHub actions workflow: Add encrypted credentials for testing with 3rd party services (e.g. Salesforce, ServiceNow, …)
- Find unit test coverage on camel-kamelet-utils module
- Leverage YAKS tests but also POC the usage of camel-jbang which might be able to provide faster turnaround times without a running Camel K infrastructure (e.g. Kind)
