Skip to content
Discussion options

You must be logged in to vote

Hey @goll-michael

Thanks for posting this with the reproducer. Actually, it looks like a case (OpenAPI as a primary, SoapUI as a secondary for a REST Service) that we never handled and that is buggy. I put some debug traces, and it appears that the problem is in the operation matching.

The operation coming from OpenAPI is GET /secondary/mediatypetextplain/example01 and we try to match it with the resource path of your test request that is /secondary/mediatypetextplain/example01 only... In that case of using it as a secondary artifact, we should probably look at some additional information as we did with Postman Collection.

Anyway, would you mind opening a bug issue on https://github.com/m…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by lbroudoux
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment