Auditing Test Quality | Bondar Academy

Lesson Summary

This video lesson discusses the process of auditing generated code using cloud code and specific skills to ensure adherence to coding rules and naming conventions. Key Concepts Model Drift: Generated code may not always align perfectly with your rules, necessitating manual checks. Code Review: Manual auditing is essential, but tools can assist in evaluating code quality. Git Diff Review: The skill can review changes in files that have not yet been committed, ensuring compliance with Playwright scripting rules. Auditing Skill Features Utilizes git to check the status and differences in branches and commits. Generates a report with recommendations for improvements based on established rules. Recommendations from the Audit CSS Class Locator: Avoid using CSS class names directly; use data-test-id attributes instead. Method Validation: Ensure actions have validation; avoid tiny methods without end validation. Assertion Ownership: Action methods should not own test goal assertions; separate them for clarity. Dynamic Waits: Implement waits before negative assertions to avoid false positives. After reviewing the recommendations, the user can apply necessary fixes and validate the tests before committing changes. This process ensures that the tests are reliable and ready for production. For further details, the auditing skill can be downloaded from the attachment provided in the lesson.