standards-testing

To prevent production code pollution, you should focus tests on real behavior rather than mocks, avoid asserting on mock existence, and stop creating test-only methods in production code to maintain production code purity.

The best way to structure mock data is to ensure your mock data structures are complete and accurate, which improves confidence by focusing tests on real behavior and integration readiness across different frameworks.

Yes, these testing standards apply to creating and reviewing test files across multiple frameworks including Jest, Vitest, Pytest, RSpec, Go testing, and JUnit, covering mocking strategies and test utilities.

You convert a failing test by applying testing guidelines to review it, removing test-only tactics, avoiding mocks, and refocusing assertions on real behavior to achieve a robust real-behavior test.

You should avoid asserting on mock existence because it causes test pollution by verifying the mock itself rather than the actual behavior, reducing confidence in integration readiness and overall code quality.