Improving test code quality with Blazor and Playwright

Don't worry, it's only test code.' How often have you heard something similar?

In this Betatalks episode, Jelle shows how to identify and fix problematic automated tests, using a Blazor app with a few Playwright tests as an example. Test code needs to be maintainable, self-documenting, and have clear intent; the easiest and most consistent way to achieve this is to care about the quality as if it was production code. Jelle discusses a few rules he follows when writing or refactoring tests, and shows how those rules play out in actual test code. He also explains how test code differs from production code and why.

Links for more information on Playwright:

• You can find both the original and the refactored test code here
• Jelle's blog about Playwright 

Also, listen to our other Betatalks about Playwright: 

• Automated testing with Playwright, NUnit and Azure Pipelines