Hey fellow hunters 👋 Wright Runner started with an actual problem a client was having; Their non-technical teams wanted to stay in the loop during test cycles and receive human-readable test results in their inbox every day. So that’s exactly what I built. Wright Runner is a hosted platform for running and managing Playwright tests without requiring everyone to understand command lines, CI pipelines, or raw test logs. Connect a GitHub/Azure/Codeberg repository and your team can: - Run Playwright tests on demand or on a schedule - Follow execution through live logs - Review full HTML reports and run history - Receive email reports when results need attention - Use AI-assisted analysis to understand failures and identify what to investigate next The goal is to make end-to-end testing more accessible to the whole team. Developers and QA engineers retain the technical detail they need, while product owners, project managers, and other stakeholders get a clear view of whether important user journeys are working. Wright Runner is intended especially for small development teams that already use Playwright—or want to—but do not want to build and maintain dedicated test infrastructure. It provides a shared, straightforward workflow for running tests, reviewing results, and keeping everyone informed. This is still the beginning, and I’d genuinely value your feedback. How does your team currently share automated test results with non-technical colleagues? What would make that process more useful? Thanks for checking out Wright Runner! 🚀

Wright Runner

Improve your QA; run and validate PlayWright tests

Improve your QA; run and validate PlayWright tests