API tests missing java-provider-image configuration in global-ci.yml

[shawn-hurley]

Description

In global-ci.yml, the API integration tests install Konveyor WITHOUT the java-provider-image parameter, while UI integration tests install WITH it. This creates inconsistent test environments.

Location

.github/workflows/global-ci.yml

Details

API Integration Tests (lines 242-274)

Three conditional install steps, NONE include java-provider-image:

• Release 0.7 install: No java-provider-image
• Release 0.8 install: No java-provider-image
• Latest install: No java-provider-image

UI Integration Tests (lines 386-421)

All three conditional install steps include java-provider-image with tag from inputs.

Impact

• API tests run without Java provider functionality
• UI tests run with Java provider functionality
• Inconsistent test coverage for Java analysis features
• API tests may miss bugs related to Java provider integration
• Different behavior between test suites could hide issues

Questions

1. Do API tests intentionally not need the Java provider?
2. Is this an oversight from when Java provider support was added?
3. Should both test suites use the same configuration?

Recommendation

Add java-provider-image parameter to all three API test install steps to match UI tests.

For each of the three install steps (v0.7, v0.8, latest), add:

java-provider-image: "quay.io/konveyor/java-external-provider:<inputs.tag>"

Related Files

• .github/workflows/global-ci.yml:242-274 (API tests - missing java-provider)
• .github/workflows/global-ci.yml:386-421 (UI tests - has java-provider)