AI Prompts for Reduce Over-Mocking in Tests

Please quote the last test output from the test suite that indicates a mock was used excessively. Identify the specific function that was mocked and explain how its behavior differs from the expected real behavior in this context. Additionally, provide suggestions on how to adjust the tests to reduce reliance on mocking and improve the accuracy of the test results.

Please analyze the following test file for the component that is over-mocked: [TEST FILE]. Identify the number of dependencies that are mocked and specify which real interactions are being ignored. Provide a summary of your findings, including potential impacts on the test coverage and suggestions for improving the test to better reflect real interactions.

Please interpret the following instruction regarding creating tests that balance mocking and real behavior. Explain your understanding of the differences between using mocks and actual implementations in testing scenarios. Additionally, provide a brief overview of the advantages and disadvantages of each approach, and suggest best practices for determining when to use one over the other in the context of testing.

Please provide a structured comparison of the expected versus actual behavior for the last test conducted on [TEST NAME]. In your response, outline the specific validation objectives of the test, detailing what the test was intended to verify and what it actually confirmed. Additionally, highlight any discrepancies between the expected outcomes and the results observed, and suggest potential reasons for these differences.

Please analyze the last test results and identify the specific rule or constraint regarding mocking that was violated. Provide a detailed explanation of the violation, including the exact clause from the documentation that outlines the acceptable use of mocks. Format your response to include the violation description, the quoted clause, and any relevant context that may help in understanding the issue.

In the test located at [FILE]:[LINE], replace the mock implementation of [SPECIFIC FUNCTION] with a real instance of the function. Confirm that the test now interacts with the actual implementation rather than the mock version. Provide a brief explanation of how this change affects the test outcomes and any potential implications for test reliability.

Rewrite the test for [COMPONENT] to utilize real dependencies instead of mocks. Ensure that the test accurately reflects the actual behavior and interactions of the component in a real environment. Provide a detailed explanation of how the real dependencies improve the test's reliability and any changes made to the test structure.

Please modify the test located at [FILE]:[LINE] to reduce the number of mocks utilized. Identify and retain only the mocks that are essential for the test to execute successfully. After making the changes, provide a brief explanation of which mocks were removed and why, as well as any impact this has on the test's functionality.

Update the test for [COMPONENT] to ensure it follows the format: 'Test [NAME] should interact with [REAL DEPENDENCY] and verify [EXPECTED OUTCOME].' Make sure that the test is designed to use real interactions instead of mocks, and provide a brief explanation of how this change improves the reliability of the test. Additionally, outline any potential challenges that may arise from this update and how to address them.

Please review the imports in the test file located at [FILE]. Identify any missing real dependencies that should be included and provide a list of the necessary imports. Additionally, suggest ways to minimize the use of mocks in the file, explaining the benefits of each change you recommend.

Please execute the updated test for [COMPONENT] using real dependencies and verify that it passes successfully. If there are any failures, provide a detailed report outlining the causes of each failure and any relevant error messages. Format the report to include the test results, a summary of the issues encountered, and suggested solutions for each failure.

Please provide a detailed diff of the test file before and after the changes related to the use of mocks. Highlight the specific lines where mocks were removed and replaced with real dependencies, and explain the significance of these changes. Additionally, summarize how these modifications improve the test's reliability and accuracy in reflecting the actual behavior of the code.

Replay the original failing test scenario for [TEST NAME] to verify that it now passes with real interactions. Please document any discrepancies you observe during the replay, including specific details about what differs from the expected outcome. Additionally, provide a summary of the changes made that may have resolved the issue.

Please verify that the updated test for [TEST NAME] handles edge cases effectively. Run the test using a variety of inputs, including [EDGE CASE INPUTS], and confirm that the outcomes match the expected results. Provide a summary of any discrepancies and suggest improvements if necessary.

Please verify the output state of the test for [COMPONENT] after implementing the changes. Analyze the results to ensure that they accurately reflect the expected behavior of the real implementation. Provide a detailed comparison between the actual output and the expected output, highlighting any discrepancies and suggesting potential reasons for any differences observed.

Before creating tests for [PROJECT NAME], ensure that mocks are only used when necessary. If a real dependency can be used, it must be included in the tests. Never mock critical interactions that could affect the reliability of the tests. Provide this guideline in a clear and concise format that can be easily referenced during the testing process.

Please create a test creation template that includes a detailed checklist for writing tests. The checklist should contain the following items: 1. Identify dependencies, 2. Use real instances where possible, and 3. Limit mocks to non-critical paths. Format the template with clear headings for each section, and provide space for notes or comments on each checklist item to enhance understanding and implementation.

Draft a project specification message that clearly states the following: "All tests must validate real behavior. Mocks should only be used when absolutely necessary and must be documented." Ensure the message is concise and emphasizes the importance of maintaining test integrity while providing guidelines for the use of mocks. Format the message in a professional tone suitable for team communication.

Establish a naming convention for tests that emphasizes real behavior. The format should be: 'Test[COMPONENT]WithRealDependencies'. Please provide examples of how this naming convention can be applied to different components, and explain why this approach enhances clarity and understanding in test cases.

Please create a self-check request for the agent regarding test validity. The request should include the following: 'Before finalizing tests, confirm that all mocks are necessary and that real dependencies are included where possible.' Ensure that the final output is formatted as a clear checklist that can be easily followed.