You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some part of the Quakurs test infrastructure automatically sets the RestAssured configuration for each test. In my case I would like to control this port manually as part of test resource to hook the prism OpenAPI validation proxy into the test harness. Is there any chance to control which port gets configured for RestAssured in a central place?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Some part of the Quakurs test infrastructure automatically sets the RestAssured configuration for each test. In my case I would like to control this port manually as part of test resource to hook the prism OpenAPI validation proxy into the test harness. Is there any chance to control which port gets configured for RestAssured in a central place?
What I tried is the following:
However,
RestAssuredURLManager
seems to be run for every test. Therefore, my custom port is overwritten.What I'd like to avoid is having to make modifications to each test class to get this working. Therefore, a central place would be a lot nicer.
Beta Was this translation helpful? Give feedback.
All reactions