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
This stems from the enhancement in #1675 when I tried to implement it.
Adding @MockServerConfig annotations to a class is not respected if you have multiple mock server configs, but for a certain test, only 1 of the providers is used.
You can see in that project that in the test which uses both mocks from both providers the mock server ports are respected, but in tests that only use a single mock provider, the ports set in the MockServerConfig are not respected.
The text was updated successfully, but these errors were encountered:
👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-930). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.
This stems from the enhancement in #1675 when I tried to implement it.
Adding
@MockServerConfig
annotations to a class is not respected if you have multiple mock server configs, but for a certain test, only 1 of the providers is used.I created a simple reproducer project at https://github.com/edeandrea/pact-multi-provider. The main
README.md
file has all the details.You can see in that project that in the test which uses both mocks from both providers the mock server ports are respected, but in tests that only use a single mock provider, the ports set in the
MockServerConfig
are not respected.The text was updated successfully, but these errors were encountered: