AI Prompts for Diagnosing Always-Passing Tests

Please quote the exact output of the test results from the console log for the test function [TEST FUNCTION NAME] that is always passing. Compare this output against the expected behavior defined in the test case [TEST CASE NAME]. Additionally, provide an analysis of any discrepancies between the actual output and the expected behavior, and suggest potential reasons for the consistent passing of this test.

Please analyze the assertions made in the test file located at [FILE_PATH]. Determine if each assertion is correctly validating the implementation and provide feedback on any that may be incorrect or insufficient. Additionally, suggest improvements or modifications to enhance the effectiveness of the tests. Format your response in a structured manner, listing each assertion and your analysis.

Please interpret the following test instructions: [TEST INSTRUCTIONS]. Provide a detailed explanation of your understanding, highlighting any potential areas of misunderstanding that could result in incorrect test outputs. Ensure your response covers the key elements of the instructions and any assumptions you are making. Format your interpretation in a clear and structured manner.

Compare the expected behavior versus the actual behavior of the tests in the context of [PROJECT NAME]. For each test case, create a detailed list that includes the specific expected outcomes and the actual outcomes that are being reported. Additionally, highlight any discrepancies between the expected and actual results, and suggest potential reasons for these differences. Format the output in a table with columns for Test Case, Expected Outcome, Actual Outcome, and Discrepancy Explanation.

Identify the specific rule or constraint that is being violated in the test implementations related to the testing framework's guidelines for writing assertions. Please quote the rule directly and provide a brief explanation of why this violation is significant. Additionally, suggest a corrective action to ensure compliance with the framework's standards. Format your response in a clear and structured manner.

Please review the test located at [FILE_PATH] and analyze the assertion found at [LINE_NUMBER]. The original assertion is: [PASTE]. I need you to correct it by changing it to: [NEW_ASSERTION]. Before applying the change, please provide me with the diff output that highlights the modification made.

Rewrite the test case located in [FILE_PATH] to ensure it accurately tests the intended functionality. Focus on updating the assertions to correctly validate the expected outcomes. Please provide the revised code along with a brief explanation of the changes made and how they improve the test's accuracy.

In the setup function of the test located at [FILE_PATH], please modify the initialization of the component to ensure it accurately reflects the current state. The original setup is as follows: [PASTE]. Update this setup to the following: [NEW_SETUP]. Ensure that the changes maintain the integrity of the tests and document any potential impacts on the test outcomes.

Check the test file at [FILE_PATH] for adherence to the required format. Ensure that all test cases follow the structure: 'it should [EXPECTED_BEHAVIOR]'. After reviewing, provide a detailed list of any deviations found, including the specific line numbers and a brief explanation of how each case deviates from the required format.

Please verify the dependencies in the file located at [FILE_PATH] to ensure that all necessary testing libraries are included. If any libraries are missing, list them as UNVERIFIED and provide the correct import statements for each missing dependency. Additionally, summarize any potential issues that could arise from the missing dependencies and suggest how to resolve them.

Run the entire test suite located at [TEST_SUITE_PATH]. Confirm that all tests are passing and provide a detailed report of any failures, including the specific tests that did not pass and the reasons for their failure. Additionally, suggest potential fixes or improvements for any failing tests to ensure they pass in future runs.

Please provide the diff of the test outputs for the file located at [FILE_PATH] before and after the recent changes. Ensure to highlight any tests that have transitioned from passing to failing, and summarize the implications of these changes on the overall test suite. Format the output clearly, indicating the specific tests affected and their previous and current statuses.

Replay the previously failing test case located at [FILE_PATH] and confirm whether it now passes with the new implementation. Please provide the detailed output of the test run, including any relevant logs or messages that indicate the result of the test execution. Additionally, summarize any differences observed compared to the previous test run.

Identify and execute edge cases related to the tests in [FILE_PATH]. Ensure that each edge case passes successfully and provide a detailed report of the results, including any discrepancies or issues encountered during the testing process. Additionally, summarize the significance of each edge case in relation to the overall functionality being tested.

Check the state of the test file at [FILE_PATH] after modifications. Confirm that it includes the correct assertions and that the expected outcomes are clearly defined. Additionally, provide a summary of any discrepancies found and suggest necessary adjustments to ensure all tests pass successfully.

Before running tests, ensure all assertions in [TEST_FILE] validate expected outcomes. If any assertion is found to be incorrect, stop and notify the developer before proceeding.

Please create a detailed template for writing test cases that includes specific sections for setup, execution, and assertions. The template should follow this format: 'describe [FEATURE]: it should [EXPECTED_BEHAVIOR] { [SETUP_CODE]; [EXECUTION_CODE]; expect([ACTUAL_OUTPUT]).toEqual([EXPECTED_OUTPUT]); }'. Additionally, provide examples for each section to illustrate how to fill in the placeholders effectively.

Create a message to display at the beginning of each testing session that checks for essential test dependencies. The message should read: 'Before any test run: verify [DEPENDENCY_1], [DEPENDENCY_2], and [DEPENDENCY_3] are installed. If any are missing, stop and notify the developer.' Ensure the message is clear and concise, emphasizing the importance of having all dependencies in place before proceeding with the tests.

Please generate a naming convention message for enforcing assertion formats in tests. The message should clearly state that all assertions must follow the structure: 'expect([ACTUAL_OUTPUT]).toEqual([EXPECTED_OUTPUT]).' Additionally, include a brief explanation of why adhering to this format is important for code consistency and maintainability. Format the output as a concise message suitable for sharing with developers.

Create a self-check request for the agent to run prior to executing tests. The request should confirm that all tests in [TEST_FILE] have valid assertions. If any assertions are found to be invalid, the agent should stop execution and report the specific issues encountered. Please format the output as a clear message indicating the status of the assertions.