mock-contract-advisor

To prevent over-mocking and recursive mocks, you should generate mock contract checklists and rules that explicitly define input/output contracts for mocked services. This ensures tests accurately reflect system interactions without creating recursive dependencies or excessive mocking anti-patterns.

A mock contract defines clear input/output parameters, expected responses, and error conditions for mocked services like external APIs or databases. It improves test design by ensuring mocks are not overly complex and reliably reflect actual system interactions during test execution.

You can define mock strategies for external APIs and databases by generating a mock contract design report based on your test suites and design documents. This process assesses complexity and identifies risks specifically for third-party service integrations.

Yes, this mock contract advisor explicitly supports L2 and L3 project levels. It generates mock contracts, assesses integration complexity, and identifies risks for external APIs, databases, and third-party services tailored to these specific project tiers.

You should create mock contracts for payment gateway integration when defining your mock strategy. This ensures the contract clearly specifies request parameters, expected responses, and error conditions while verifying the mock itself is not overly complex or dependent on other mocks.

Stub contracts for third-party services can lead to anti-patterns like global mocks and excessive mocking if not properly constrained. They may also fail to reflect system interactions accurately if the mock itself becomes overly complex or dependent on other recursive mocks.