What

Overrides equals() and hashCode() in AbstractLogicalMatcher to compare the full operands list, not just the inherited expectedValue.

Why

AbstractLogicalMatcher inherits equals()/hashCode() from StringValuePattern, which only compares the expectedValue field. The constructor passes only the first operand's expected value to the parent via checkAtLeast2OperandsAndReturnFirstExpected().

This means two LogicalAnd/LogicalOr instances with the same first operand but different subsequent operands are incorrectly treated as equal:

LogicalAnd matcher1 = new LogicalAnd(WireMock.equalTo("A"), WireMock.equalTo("B"));
LogicalAnd matcher2 = new LogicalAnd(WireMock.equalTo("A"), WireMock.equalTo("C"));

matcher1.equals(matcher2); // true — should be false

This causes incorrect stub deduplication when ignoreRepeatRequests is used with a StubMappingTransformer that produces logical AND/OR body patterns.

Changes

• AbstractLogicalMatcher.java — override equals() to also compare operands list; override hashCode() to include operands
• LogicalAndTest.java — added test: same first operand, different later operands → not equal
• LogicalOrTest.java — added same test for LogicalOr

Fixes #3353

Made with Cursor