AI Prompts for Preventing Test Failures After Edits

Please provide a comprehensive list of all recent changes made in the project. For each change, highlight any that could potentially impact the outcomes of the tests. Additionally, summarize the implications of these changes on the overall project and testing strategy, including any risks or considerations that should be addressed moving forward.

Please analyze the test results from the latest run of my project. Identify all tests that are currently failing and provide detailed information on each failure, including any error messages and stack traces associated with them. Additionally, summarize potential reasons for these failures based on the error messages and suggest possible next steps for troubleshooting. Format the output in a clear, structured manner that allows for easy review and follow-up actions.

Analyze the recent changes made to the codebase and identify which specific edits may be causing the test failures. Provide a detailed explanation of your reasoning, including any patterns or correlations you observe between the changes and the failures. Additionally, suggest potential solutions or adjustments that could resolve these issues. Format your response in a structured manner, outlining the changes, the associated failures, and your recommendations.

Please review the dependencies of the failing tests in the project. Identify any recent changes in these dependencies that could have contributed to the test failures. Provide a detailed analysis of each dependency, including the version numbers, the nature of the changes, and any potential impact on the tests. Additionally, suggest possible solutions or workarounds for addressing the identified issues. Format your findings in a clear report that outlines the dependencies, changes, and recommendations.

Please generate a detailed code coverage report for the recent changes made in the codebase. Identify and highlight any areas where code coverage has decreased, particularly those that may be connected to the recent test failures. Include specific metrics such as the percentage of code covered, the lines of code affected, and any relevant files or modules. Additionally, provide recommendations on how to improve coverage in these areas to prevent future test failures. Format the report in a clear and organized manner for easy review.

Please help me identify the specific change that is causing the test failure in my project. Once identified, provide a detailed explanation of how to revert this change effectively. Additionally, confirm that the tests pass again after the reversion and outline any potential implications this reversion may have on the overall functionality of the project. Include steps to ensure that similar issues do not arise in the future.

Identify the problematic change in the code that is causing test failures. Suggest targeted fixes that will maintain the intended functionality while ensuring that all existing tests pass successfully. Provide a detailed explanation of the changes you propose, including any potential impacts on related components and how you will verify that the fix resolves the issue without introducing new problems. Format your response as a step-by-step guide that includes code snippets where applicable.

Propose a detailed refactor of the affected code in [SPECIFIC MODULE OR FUNCTION NAME] to enhance its stability and prevent similar test failures in the future. Identify the key areas in the code that contribute to instability and suggest specific changes or improvements. Additionally, explain how these changes will address the current issues and outline any potential impacts on existing functionality. Provide examples of best practices that can be applied in this refactor to ensure long-term reliability.

Please review the current failing test cases for the project related to [PROJECT NAME]. Identify the specific reasons for their failure and suggest detailed updates or additions to the tests that would improve their effectiveness in handling the recent changes made in the codebase. Include explanations for each suggested change, and if applicable, provide examples of how the updated tests should be structured. Ensure that the recommendations align with best practices for testing in [PROGRAMMING LANGUAGE] and cover edge cases that may have been overlooked.

Analyze the fixed code for any potential side effects. Identify any areas where the changes might lead to unintended consequences or new issues. Provide a detailed report on your findings, including specific examples of any side effects detected and recommendations for further testing or adjustments needed to ensure the code functions as intended without introducing new problems.

Please execute the full test suite for the project to confirm that all tests pass after the recent fix. Provide a detailed summary of the test results, including the number of tests run, how many passed, how many failed, and any errors or failures that occurred. Additionally, include any relevant logs or output that can help in understanding the results. Format this information in a clear and organized manner for easy review.

Please reproduce the scenario that caused the original test failure related to [SPECIFIC ISSUE]. Document the steps taken to replicate the issue and confirm whether the problem still occurs. If the issue is resolved, provide a summary of the changes made that led to the fix, and if applicable, include any additional tests that were conducted to ensure the resolution is stable. Format your findings in a clear report that outlines the original failure, the reproduction steps, and the confirmation of the fix.

Please review the integrity of the codebase after the recent fix. Check for any new warnings or errors that may have been introduced during the process. Provide a detailed report that includes the specific files or sections of code that were affected, any issues found, and recommendations for resolving them. Additionally, summarize the overall health of the codebase and suggest any best practices to maintain its integrity moving forward.

Please verify that the intended functionality of the recent changes made to [SPECIFIC FEATURE OR FUNCTIONALITY] is preserved after the fix. Outline the specific tests that should be conducted to ensure that all aspects of the functionality are working as expected. Include details on any edge cases or scenarios that should be considered during the validation process. Provide a summary of the expected outcomes for each test case, and indicate how to document any discrepancies or issues that arise.

Generate an updated code coverage report for the recent changes made in the codebase. Ensure that the coverage percentage has not decreased as a result of the fixes implemented. Include a comparison with the previous coverage report, highlighting any areas where coverage has improved or remained the same. Additionally, provide recommendations for any areas that may need further testing to maintain or enhance coverage. Format the report clearly, with sections for summary, detailed coverage metrics, and suggested next steps.

Draft a new rule for CLAUDE.md aimed at preventing similar test failures based on the recent issue encountered. The rule should clearly outline the conditions that trigger the failure, the recommended practices to avoid these issues, and any specific guidelines that should be followed. Ensure the language is precise and actionable, and format the rule in a way that can be easily integrated into the existing documentation. Include examples where applicable to illustrate the rule's application.

Please add a detailed code comment above the fixed function in the codebase. The comment should clearly explain the specific constraint that led to the fix, including any relevant context or conditions that future developers should be aware of. Additionally, outline the potential implications of not adhering to this constraint and provide guidance on how to avoid similar issues in the future. Ensure the comment is concise yet informative, ideally formatted in a way that is easy to read and understand.

Create a comprehensive checklist for reviewing code changes before committing them to the repository. The checklist should include specific steps to ensure test stability, such as verifying that all existing tests pass, running new tests, checking for code quality and adherence to style guidelines, and ensuring that documentation is updated. Additionally, include a section for peer review and any necessary approvals. Format the checklist in a clear, organized manner with bullet points for easy readability.

Please create a comprehensive session opener guide for developers that outlines essential checks to perform before starting a new session. The guide should include a checklist of key items such as verifying the development environment setup, ensuring all necessary tools and resources are available, confirming that the latest code changes are pulled and tested, and reviewing any relevant documentation or notes from previous sessions. Format the guide in a clear, step-by-step manner, and aim for a length of at least one page to ensure thoroughness.

Help me establish a project convention for managing changes that impact tests in software development. Outline a clear guideline that includes: the process for notifying team members about changes, how to assess the impact on existing tests, and the steps to update or create new tests accordingly. Additionally, include best practices for documentation and communication to ensure everyone is aligned and aware of the changes. Format this guideline as a checklist that can be easily referenced by the team.