test(kiali): contract tests

[josunect]

Automated Consistency Tests: Verify MCP Tool Definitions against Kiali API Routes

How do we know that APIs used by the consumer (kiali mcp) still exist and return what it expects?

• Kiali mcp declares what is using
• It is expected to run these tests by Kiali to verify those expectations in CI

Contract tests keep coupling low because they only describe:

• endpoints
• request/responses
• status codes

TODO:

• Kiali CI: Use these tests: [kiali-mcp] Add workflow to validate mcp routes kiali/kiali#9018 (It will be merged after this PR)
• A test that validates that all the routes declared in endpoints.go are tested

[aljesusg]

LGFM

[aljesusg]

cc @Cali0707 Can we merge this test validation?

[manusa]

This seems reasonable. However, I fail to see why the backend tests are maintained here if they are executed from a different repo.

[josunect]

This seems reasonable. However, I fail to see why the backend tests are maintained here if they are executed from a different repo.

That's because they are testing the endpoints implemented by the other repo (Maintained by the same team). So, if any endpoint is modified, the tests will fail, and the way to fix it would be:

• Or update the endpoints used by Kiali MCP accordingly (And the tests)
• Or version the Kiali endpoints to keep compatibility and don't break the Kiali MCP

[Cali0707]

nit: can we make this something like kiali-contract ? Just to be a bit more explicit about which contract we are testing