Hi Aran.
Thanks for coming back to me on this.
The expandedPath value was set to
/APITST/v1.0/TST/my_apiwhich of course could not be found in the openapi spec.
Meanwhile by more testing, I know why. The Service Base value should not include the trailing star*.
So , Service Base set to :
/APITST/v1.0*does not work
But using it without the asterisk is working. Obviously the Service Base value is just removed from the beginning of the incoming service uri.
I misunderstood the docs stating: "Note: The service URI must end with '/*' ..."
Just quite clear after knowing how it works.
Thanks and kind regards
....Michael
Original Message:
Sent: 11-24-2021 01:41 PM
From: Aran White
Subject: validate openapi document assertion failure?
Do you get a specific error ?
------------------------------
Aran White - [JobTitle]
[CompanyName]
[State]
Original Message:
Sent: 11-24-2021 04:30 AM
From: Michael Müller
Subject: validate openapi document assertion failure?
Hi Team.
I am trying to use the "validate openapi document" assertion.
My openapi doc includes path defintions of
...
path:
/TST/my_api:
The GW service resolutionpath is specified as /APITST/v1.0/TST/*
The test postman call is done to https://gw:port/APITST/v1.0/TST/my_api
The Service Base property of the assertion is specified as /APITST/v1.0*
Unfortunately the validate assertion fails, and I don't know what I am doing wrong.
Does anyone has any idea ?
Thanks
....Michael