Assertions Generation and Agent Auto-Debugging | Bondar Academy

Lesson Summary

In this lesson, we explore how to use Copilot to suggest missing assertions for API tests. Here’s a structured overview of the key points discussed: Setting Up the Environment Modify playerconfig.ts to include a flag for the HTML reporter as openNever . This prevents the automatic opening of the HTML reporter when tests fail, allowing Copilot to continue working in the same terminal. Testing with Copilot We begin with a test for fetching articles that already includes some assertions. The goal is to see if Copilot can suggest additional useful assertions based on the response JSON object. Steps to Use Copilot Run the test to obtain the JSON response object. Copy the response and prompt Copilot by asking for useful assertions while specifying what to exclude (e.g., data type validations). Review the suggested assertions, such as: verifyArticleSorted verifyEachArticleHasRequiredField verifyArticleCount Select meaningful assertions to keep, such as verifySlugMatchTitleFormat . Implementing and Testing Assertions After selecting an assertion, provide business context for validation requirements. For instance, the slug should match the title format with specific rules. Running Tests Use the command npx player test -g to run specific tests. If a test fails, Copilot can analyze the error and attempt to fix it automatically. Key Takeaways Copilot can interact with the terminal and self-correct based on error messages. Using a more advanced model like Cloud 3.5 may yield better results. Always verify that assertions remain meaningful after Copilot's modifications. In conclusion, Copilot's ability to suggest and refine assertions can enhance API testing efficiency, but careful oversight is necessary to ensure the validity of the assertions.