Test Steps Decorator | Bondar Academy

Lesson Summary

This lesson focuses on improving the visibility of test failures when using page objects in testing frameworks. While page objects simplify writing and reading tests, they can obscure the reasons for test failures, making debugging difficult. Identifying the Problem The instructor demonstrates a failure in two tests related to the FormLayouts page. When the tests fail, the stack trace only indicates the method where the failure occurred, not which specific test or step failed. Current Reporting Limitations Stack traces do not specify which test step failed. Test reports show the same failure details, lacking clarity on the specific test body line that caused the failure. Proposed Solution To enhance reporting, the instructor introduces the PlayWrite method test.step , which can wrap code to provide descriptive reporting. However, this method requires extensive coding, which can be cumbersome. Using a TypeScript Decorator Instead, the instructor suggests creating a TypeScript decorator function, which can be reused across multiple page objects. This decorator will automatically provide detailed reporting without extensive code modifications. Implementation Steps Create a new folder named helpers and a file testStepDecorator.ts . Import the necessary PlayWrite test function and define the decorator function. Modify the decorator to suppress unnecessary logging while retaining detailed call stack traces. Import and apply the decorator to page object methods. Results After implementing the decorator, the test reports now clearly indicate which specific test step failed, providing better insight into debugging issues. This adjustment enhances the overall test visibility and understanding. In conclusion, the lesson emphasizes the importance of clear reporting in testing frameworks and offers a practical solution to improve test failure visibility.