MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding).
Describe the issue
The order in which expectations with path parameters for different paths are registered seems to influence whether a verification passes or not.
What you are trying to do
I have multiple expectations configured for different paths, containing path parameters. I try to execute a verification based on the path and path parameters.
MockServer version
5.13.2
To Reproduce
I created the tests below to illustrate the problem. The tests are similar except for the order in which the expectations are configured.
Expected behaviour
I expect both tests to pass. The order in which expectations for unrelated requests are registered should not influence verification.
The difference seems to be in the recorded path parameters for the request
Describe the issue The order in which expectations with path parameters for different paths are registered seems to influence whether a verification passes or not.
What you are trying to do I have multiple expectations configured for different paths, containing path parameters. I try to execute a verification based on the path and path parameters.
MockServer version 5.13.2
To Reproduce
I created the tests below to illustrate the problem. The tests are similar except for the order in which the expectations are configured.
Expected behaviour I expect both tests to pass. The order in which expectations for unrelated requests are registered should not influence verification.
The difference seems to be in the recorded path parameters for the request
I don't understand why the fooId path is recorded for failing case.
MockServer Log