Radberi-TestingAntiPatterns

Avoid testing mock behaviour by replacing complex mocks with actual in-memory databases or containerized services. Use mocks strictly for external dependencies to ensure tests accurately reflect real-world behaviors rather than validating mock interactions.

Over-mocking dependencies creates false test pass states by validating mock interactions rather than actual business logic. It reduces test reliability by disconnecting tests from real-world behaviors, making refactoring risky and test failures misleading.

Prevent test-only method pollution by maintaining strict separation between production code and test utilities. Never add test-specific methods or exposure to your production classes, as this compromises code safety and violates clean dependency management practices.

Use in-memory databases or test containers instead of mocks when verifying complex dependencies that require real-world behavior simulation. This approach ensures tests reflect actual component actions rather than mock interactions, improving overall test reliability.

Replace complex mocks with in-memory databases or containerized services to improve test reliability. This ensures tests accurately reflect real-world behaviors and prevents false pass states caused by testing mock behaviour instead of actual component actions.