AI Prompts for Preventing Test Breakages in Lovable

Please provide a comprehensive list of all recent changes made to the codebase. For each change, highlight any modifications that could potentially impact existing tests, including changes to functions, variables, or dependencies. Additionally, summarize the overall impact of these changes on the functionality and stability of the codebase. Format the response in a clear, organized manner, categorizing changes by type and significance.

Please provide the latest test logs from the testing environment. Identify and summarize any specific errors or failures that have occurred since the last successful run, including the timestamps and error messages associated with each issue. Additionally, categorize the errors by severity and suggest potential next steps for troubleshooting each type of failure. Format the results in a clear and organized manner for easy review.

Please analyze the error messages in the test logs and provide detailed explanations for each one. For each error, describe what it indicates about the recent code changes, including potential causes and implications for the overall functionality. Additionally, suggest possible solutions or next steps to address each error. Format your response in a clear, structured manner, with each error and its explanation listed separately.

Please analyze the current test coverage for the project and identify any areas where coverage has decreased after recent changes. Provide a detailed report that includes specific files or modules affected, the percentage of coverage before and after the changes, and any potential reasons for the decrease. Additionally, suggest actionable steps to improve coverage in these areas and ensure that all critical functionalities are adequately tested. Format the findings in a clear and structured manner, highlighting the most significant issues first.

Please compare the current code version with the last stable version. Identify and highlight any differences that may impact test outcomes, including changes in functionality, performance, or dependencies. Provide a detailed report that outlines each difference, categorizing them by their potential effects on existing tests. Include recommendations for adjustments or considerations that should be made to ensure test reliability moving forward.

Identify the specific changes that led to the recent test failures in the project. Provide a detailed explanation of why these changes were problematic, including any potential impacts on the overall functionality and performance of the application. After outlining the issues, suggest a plan for reverting these changes, ensuring that the tests can pass successfully again. Additionally, recommend any further steps that should be taken to prevent similar issues in the future.

Please identify the tests that have been affected by recent changes in the codebase. For each affected test, provide a detailed analysis of how it needs to be updated to align with the current implementation. Include specific examples of the changes required, any dependencies that may be impacted, and ensure that the updated tests maintain their original intent while reflecting the new code structure. Format your response as a checklist, with each item clearly outlining the test name, the necessary updates, and any additional notes for context.

Please analyze the code provided and identify the specific lines that are causing test failures. For each error, explain why it is occurring and provide a corrected version of the code. Additionally, include a brief explanation of the changes made and how they resolve the issue. Ensure that the response is clear and structured, so it can be easily understood by someone reviewing the code.

Refactor the existing codebase to enhance compatibility with the current test suite. Focus on identifying and resolving any potential conflicts that may arise during the refactoring process. Ensure that the changes maintain the original functionality and do not introduce any new issues or bugs. Provide a summary of the modifications made, including any specific areas of the code that were adjusted and the reasoning behind those changes. Additionally, outline the testing strategy to verify that all existing tests pass successfully after the refactor.

Please enhance the error handling in the existing codebase to prevent similar test failures in the future. Detail the specific changes you implement, including any new error messages, logging mechanisms, or exception handling strategies that are added. Additionally, explain how these enhancements improve the robustness of the code and contribute to better test reliability. Provide examples of potential error scenarios that will now be handled more effectively.

Please execute all tests related to the recent fixes made in [SPECIFIC AREA OR MODULE]. I need a detailed report of the test results, including which tests passed and which failed, along with any error messages or issues encountered during the testing process. Additionally, provide a summary of the overall success rate of the tests and any recommendations for further actions if issues persist. Format the results in a clear and organized manner for easy review.

Please confirm that the specific errors previously identified in the system are no longer occurring. For each error, provide a detailed before-and-after comparison that highlights the changes made and the current status of the system. Include specific examples of the errors, the steps taken to resolve them, and any relevant metrics or logs that illustrate the resolution. Format your response in a clear and organized manner, ensuring it is easy to understand the improvements made.

Please re-evaluate the test coverage for the project after the recent fixes have been implemented. Ensure that it meets the required standards and identify any areas where coverage has improved. Provide a detailed report that includes specific metrics on coverage percentages, any newly added tests, and highlight sections of the code that now have adequate coverage. Additionally, suggest any further improvements or tests that could enhance the overall coverage.

Please provide a detailed summary of all code changes made during the fix process for [PROJECT NAME]. For each change, confirm its stability and ensure that it does not introduce any new test failures. Include specific information about the tests that were run, the results of those tests, and any relevant metrics that demonstrate the impact of the changes. Additionally, highlight any areas of concern or potential risks associated with the code changes.

Please review the latest test logs for [PROJECT NAME] and summarize the findings. Confirm whether there are any new errors or warnings present since the last review. If there are issues, categorize them by severity and provide recommendations for resolution. Additionally, include any relevant metrics or trends observed in the logs that could help in understanding the overall test performance.

Draft a new rule for CLAUDE.md that aims to prevent test breakages caused by similar changes in the future. The rule should include specific guidelines on how to identify potential issues before they arise, as well as best practices for writing tests that are resilient to changes. Please provide the exact text to be added to CLAUDE.md, ensuring it is clear, concise, and actionable for developers. Additionally, include examples of common scenarios where this rule would apply and how it can improve overall code stability.

Create a comprehensive checklist to follow at the beginning of any coding session that involves making changes to the codebase. The checklist should include specific steps to prevent test breakages, such as reviewing existing tests, ensuring all dependencies are up to date, and running a preliminary test suite. Additionally, include steps for documenting changes and communicating with team members about the modifications being made. Format the checklist in a clear, easy-to-follow manner, with each step clearly outlined.

Review the following code snippet: [INSERT CODE SNIPPET]. Identify areas where potential test breakages could occur and suggest appropriate comments to insert that will warn future developers. Each comment should clearly explain the reason for the warning and what specific conditions might lead to a test failure. Format your response by providing the exact comment text for each identified area, ensuring that the comments are concise yet informative.

Help me establish a comprehensive protocol for testing code changes before deployment. The protocol should include detailed steps for verifying the stability of tests, including criteria for passing and failing tests, methods for identifying flaky tests, and procedures for addressing any issues found during testing. Additionally, outline the roles and responsibilities of team members involved in the testing process, and suggest best practices for maintaining and updating the testing suite over time. Format this as a clear, step-by-step guide that can be easily followed by the development team.

Draft a comprehensive set of code review guidelines aimed at preventing test breakages in software development. The guidelines should cover key practices such as ensuring thorough test coverage, verifying that new code does not introduce conflicts with existing tests, and emphasizing the importance of running all tests before merging changes. Include specific examples of common pitfalls to avoid during code reviews and suggest best practices for reviewers to follow. Format the guidelines in a clear, numbered list for easy reference.