kaoto-backend
kaoto-backend copied to clipboard
Provide QuarkusIntegrationTest for major features
Is your feature request related to a problem? Please describe.
Providing QuarkusIntegrationTest allows to test that the native executable. It is very useful to detect bad packaging of resources.
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context
first one (and very minimal) test added here https://github.com/KaotoIO/kaoto-backend/pull/338
Listing of JVM test for api module which can serve as a base to provide Native test:
Class | Status | Issue | Comments | Priority |
---|---|---|---|---|
CatalogWarmingUpExceptionTest | ||||
CapabilitiesResourceTest | Done (+ #683) | #426 | CapabilitiesResourceIT | High |
DeploymentsResourceTest | Done | #436 | ||
IntegrationsResourceTest | in pr for all except one test moved to a specific class | #437 | IntegrationsResourceIT | |
StepResourceTest | Done (+ #812) | #336 | StepResourceIT | High |
ViewDefinitionResourceTest | #438 | |||
DeploymentServiceTest | #439 | |||
KameletBindingDeploymentGeneratorServiceTest | #440 | |||
LanguageServiceTest | #441 | |||
GenericViewDefinitionParserServiceTest | #442 |
Should be possible for other modules but need to investigate first and maybe having the tests are the API level would be enough?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Unfortunately there was no activity but it is a really important task for the maintainability and quality of the software. Adding commen tto not have it closed. I will let the people that will work on this task checking all link substasks if they need to be reopened or if they were closed because really implemented.