AI Prompts for Reducing Over-Mocking in Tests

Please identify all the dependencies that are currently mocked in the test suite for [COMPONENT_NAME]. For each mocked dependency, provide a detailed summary explaining its intended functionality and purpose within the context of the component. Additionally, include any relevant information about how these mocked dependencies interact with the component during testing. Format your response in a clear list, with each dependency followed by its summary.

Analyze the test coverage for [COMPONENT_NAME] and identify the specific areas of the code that are not adequately tested because of excessive mocking. Provide a detailed report that includes the following: a summary of the current test coverage metrics, a list of the components or functions that are overly mocked, and recommendations for improving the test coverage by reducing the reliance on mocks. Additionally, suggest alternative testing strategies that could be employed to ensure comprehensive coverage of the codebase.

Review the recent test runs for [COMPONENT_NAME] and analyze the results to identify any test failures that may be attributed to over-mocking. For each failure, provide a detailed explanation of the issue, including the specific tests that failed, the expected outcomes versus the actual results, and any relevant context that could help in understanding why over-mocking might have contributed to these failures. Additionally, suggest potential solutions or adjustments that could be made to improve the reliability of the tests moving forward.

For the component [COMPONENT_NAME], please provide a comprehensive list of all test assertions. For each assertion, indicate whether it relies on mocked data or actual data. Additionally, explain the potential impact of using mocked data on the reliability of the tests, including any risks or limitations that may arise from this approach. Aim for a detailed analysis that helps understand how these assertions contribute to overall test effectiveness.

Analyze the interactions of [COMPONENT_NAME] as they are used in production and compare them with the mocked interactions currently implemented in tests. Identify and highlight any discrepancies between the two, focusing on areas where the mocked data does not accurately reflect real-world usage. Provide a detailed report that includes specific examples of differences, potential impacts on testing outcomes, and recommendations for aligning the tests more closely with actual usage patterns.

Please analyze the test suite for [COMPONENT_NAME] and identify any mocks that are unnecessary for the execution of the tests. For each mock you suggest removing, provide a clear explanation of why it is not essential, including how its removal could simplify the tests or improve their reliability. Additionally, outline any potential impacts on test coverage and performance after these changes are made. Present your findings in a structured format, detailing each mock and its rationale for removal.

Identify opportunities to use real data in tests for [COMPONENT_NAME] to enhance accuracy and reliability. Provide specific examples of scenarios where real data can be effectively integrated into the testing process, detailing the potential benefits and any challenges that might arise. Additionally, outline best practices for implementing real data in tests to ensure that the results are valid and meaningful.

Propose a simplified test setup for [COMPONENT_NAME] that minimizes the use of mocks while ensuring comprehensive test coverage. Detail the specific strategies and techniques that can be employed to achieve this, including any necessary configurations or adjustments to the testing framework. Explain how this approach can enhance the reliability of the tests and provide examples of scenarios where mocks can be reduced or eliminated. Additionally, outline the expected outcomes in terms of test performance and maintainability.

Identify the test logic for [COMPONENT_NAME] and analyze it to determine which parts can be refactored to minimize the reliance on mocks. Outline a detailed refactoring plan that includes specific changes to improve the test's structure and maintainability. Include recommendations for alternative approaches or techniques that can be used to achieve the same testing goals without extensive mocking. Additionally, provide examples of how the refactored tests would look and any potential impacts on test coverage or performance.

Please analyze the current mocks used for [COMPONENT_NAME] and identify areas where their accuracy can be improved to better reflect real-world scenarios. Provide a detailed list of specific improvements that can be made, including examples of how these changes would enhance the testing process. Additionally, explain the potential impact of these improvements on the overall reliability of the tests and any considerations that should be taken into account during implementation.

Please run the updated test suite for [COMPONENT_NAME] and generate a detailed report on the results. Include information on the overall pass rate, any tests that failed, and specific areas where test reliability has improved. Additionally, provide insights into potential reasons for any failures and suggest next steps for addressing them. Format the report in a clear and organized manner, with sections for summary, detailed results, and recommendations.

Analyze the test results for [COMPONENT_NAME] in detail. Confirm whether any reported failures are genuine issues that need to be addressed or if they are simply artifacts resulting from over-mocking in the tests. Provide a summary of your findings, including specific examples of any failures that are real versus those that are not, and suggest potential steps to resolve any genuine issues identified. Additionally, include recommendations for improving the testing approach to minimize over-mocking in the future.

Please validate the test coverage for [COMPONENT_NAME]. Assess whether the current tests include real interactions and scenarios that reflect how the component will be used in practice. Provide a detailed report on any gaps in coverage, suggest additional tests that should be implemented to improve reliability, and outline the importance of each suggested test in ensuring comprehensive coverage. Additionally, include recommendations on best practices for maintaining test coverage moving forward.

Please verify the number of mocks in the test suite for [COMPONENT_NAME]. Provide a detailed comparison of the current number of mocks versus the previous count, and confirm that all tests are still passing successfully. Additionally, summarize any potential impacts this reduction may have on test coverage and performance. If there are any tests that have failed, please list them along with the reasons for failure and suggestions for resolution.

Please review the test assertions for [COMPONENT_NAME] and confirm that they are now based on real data and interactions. Summarize the specific changes made to the assertions, detailing how they improve accuracy and reliability. Include any examples of how the new assertions differ from the previous ones and explain the impact these changes may have on overall test outcomes. Additionally, provide recommendations for any further adjustments or enhancements that could be beneficial.

Please draft a new rule for CLAUDE.md that addresses the use of mocks in tests. The rule should clearly define what constitutes acceptable and unacceptable use of mocks, including specific scenarios where mocks are discouraged. Additionally, provide guidelines on alternative testing strategies that can be employed instead of mocks. Ensure the rule is concise yet comprehensive, suitable for inclusion in a coding standards document.

Please add a comment in the test code for [COMPONENT_NAME] that explains the rationale for reducing mocking. The comment should clearly articulate the reasons behind this decision, including any benefits such as improved test reliability, easier debugging, or better alignment with real-world scenarios. Ensure the comment is concise yet informative, ideally consisting of 2-3 sentences that can easily be understood by other developers reviewing the code. Provide the exact text of the comment to be included.

Create a comprehensive checklist for writing tests in [COMPONENT_NAME] that emphasizes the appropriate use of mocks. Include specific criteria that must be met before deciding to use a mock, such as the complexity of the component, the need for isolation, and potential side effects. Additionally, outline best practices for writing tests without mocks, including suggestions for integration tests and real component usage. Format the checklist with clear headings and bullet points for easy reference, ensuring it covers at least 10 key items.

Propose a detailed naming convention for test files related to [COMPONENT_NAME] that clearly indicates the level of mocking utilized in each test. The convention should differentiate between fully mocked tests, partially mocked tests, and integration tests with no mocking. Include specific examples of naming formats for each level, such as using prefixes or suffixes to denote the mocking level. Additionally, explain the rationale behind this naming convention and how it can improve clarity and maintainability in the testing process.

Design a project guard for [COMPONENT_NAME] that identifies and flags instances of excessive mocking during test creation. Explain the criteria that will be used to determine what constitutes excessive mocking and outline the specific actions the guard will take when it detects such cases. Include details on how this guard integrates with the existing testing framework, any configuration options available to developers, and the potential impact on code quality and test reliability. Provide examples of scenarios where excessive mocking could lead to issues and how the guard helps mitigate those risks.