AI Prompts for Diagnose Test Failures After Changes

Please quote the exact error message from the test output that indicates the failure for the test case in [TEST FILE]:[LINE]. Compare this error message to the expected output and provide an analysis of why the test is failing. Additionally, suggest potential reasons for the discrepancy and any steps that could be taken to resolve the issue.

Please analyze the following failing test case from [TEST FILE]: [PASTE FAILING TEST CASE CONTENT HERE]. Identify the specific changes in the code that may have caused this failure, and provide a detailed explanation of how each change impacts the test's functionality. Additionally, suggest potential solutions to fix the identified issues.

Please interpret the last instruction I provided regarding the test cases. Clearly outline your understanding of the key points and any specific details mentioned. After your interpretation, identify any potential misunderstandings or ambiguities that may need clarification before proceeding with fixing the issue.

Compare the expected behavior of the test case in [TEST FILE] with the actual behavior observed in the output. Provide a detailed list that outlines what the test was intended to verify and highlight the specific areas where it is currently failing. Include any relevant error messages or discrepancies that illustrate the differences between expected and actual outcomes.

Please analyze the last code change and identify any violated constraints. Quote the specific rule or constraint that was breached and reference the exact clause that outlines the expected behavior of the tests. Provide a detailed explanation of how this violation affects the overall functionality and suggest potential solutions to address the issue.

Please analyze the failing test case located in [TEST FILE] at line [LINE]. Identify the incorrect assertion and modify it to align with the expected output of [EXPECTED OUTPUT]. Before making any changes, provide me with a diff of the proposed modifications so I can review the adjustments.

The function in [SOURCE FILE] at line [LINE] has changed its signature and is causing the test to fail. The original signature was [ORIGINAL SIGNATURE]. Please revert the function signature back to the original while ensuring that the body of the function remains unchanged. Provide the updated code with the new signature clearly indicated.

In the file [SOURCE FILE], the variable [VARIABLE NAME] is being used incorrectly, leading to test failures. Please identify the specific lines where this variable is used and provide a corrected version that properly scopes the variable. Additionally, include a brief explanation of the changes made and how they resolve the issue.

Please review the test case in [TEST FILE] and ensure it adheres to the required format of [SPECIFIC FORMAT]. Identify any discrepancies and provide a corrected version of the test case that meets the specified format requirements. Additionally, include a brief explanation of the changes made to ensure compliance with the format.

Please verify the import statement in [SOURCE FILE] for [PACKAGE NAME]. If it is missing or incorrect, correct it to ensure that all tests can run successfully. Additionally, provide a brief explanation of the changes made and any potential impact on the existing codebase.

Please execute the test suite located in [TEST FILE] and verify that all tests pass successfully. If any tests fail, provide a detailed report of the errors encountered. Additionally, include the overall summary of the test results, indicating the total number of tests run and how many passed or failed.

Display the differences between the changes made to [SOURCE FILE] and [TEST FILE]. Provide a detailed comparison that highlights what was added, removed, or modified in each file. Additionally, summarize how these changes impact the overall functionality and correctness of the tests, ensuring that the necessary modifications were applied correctly.

Replay the original scenario that caused the test to fail. Confirm whether the changes made have resolved the issue by providing detailed output of the test results. Include any relevant logs or error messages that may assist in understanding the resolution status.

Verify the edge case related to [SPECIFIC CONDITION] in [TEST FILE]. Analyze the test results to confirm that this edge case passes successfully after the recent changes. Provide a summary of your findings, including any relevant details about the test execution and the expected versus actual outcomes.

Please verify the state of the file [TEST FILE] after the recent modifications. Check that it accurately reflects the expected changes and ensure that all test cases are functioning correctly. Provide a summary of any discrepancies found and suggest necessary adjustments to align the file with the intended outcomes.

Please create a self-check request for the agent that ensures test case integrity. The request should state: 'Before any code change, verify that all test cases in [TEST FILE] pass. If any test fails, stop the process and report the failure immediately before proceeding with any changes.' Ensure the output clearly outlines the steps taken during this verification process.

Please create a project convention message that outlines the protocol for code changes. Specifically, instruct that for any code changes, the corresponding tests in [TEST FILE] must be updated. Additionally, require that any modifications made to the tests are documented clearly in the commit message. Format this message in a clear and concise manner suitable for team communication.

Before deploying the application, please validate that all tests in [TEST FILE] pass successfully. If any test fails, prevent the deployment process and generate a detailed summary of the failures, including the names of the failed tests and the reasons for their failure. Ensure that this validation step is clearly documented in the deployment logs for future reference.

Please add a code comment guard in [TEST FILE] that states: 'Ensure all test cases adhere to the format: [SPECIFIC FORMAT]. If any test case does not comply with this format, it should trigger a test failure. Additionally, provide a brief explanation of why maintaining this format is important for test consistency and reliability.

Create a conversation-starter template for notifying the team about dependency updates. When dependencies in [SOURCE FILE] are updated, the template should prompt the team to review and update related tests in [TEST FILE]. Ensure the notification includes a reminder of the importance of maintaining test accuracy and any specific areas of concern that may need attention.