DEV Community

Maki chen
Maki chen

Posted on

"Playwright Automated Testing: Quality Auditing 100 Websites in Practice"

Building 100 websites in a day is impressive, but if 10 of them have broken images, 5 have 404 errors, and 3 have layout issues on mobile, it becomes a disaster.

Quality testing is the most commonly overlooked step in the website building process. The traditional approach is to have a QA person manually check each page one by one. With 100 websites and at least 5 pages each, just opening and visually inspecting them takes several days. And people get tired and miss things.

At HEY!BOSS 銀月數位顧問, we solve this problem with the Playwright automated testing framework. Quality auditing 100 websites takes just 2 hours with zero missed defects.

1. What Is Playwright?

Playwright is an open-source automated testing framework developed by Microsoft. It can control real browsers (Chromium, Firefox, WebKit) and simulate user interactions — clicking, scrolling, typing, taking screenshots — all automatically.

Compared to Selenium, which you may have heard of, Playwright has several clear advantages:

  • Faster execution — A more modern architecture makes it 2-3x faster than Selenium

  • Auto-waiting — No need to write sleep or wait statements; Playwright automatically waits for elements to load before interacting

  • Multi-browser support — Native support for Chromium, Firefox, and WebKit engines

  • Powerful selectors — Supports text, CSS, XPath, ARIA roles, and other element location methods

2. HEY!BOSS's Three-Round Quality Audit

We don't just run a test once and call it done. HEY!BOSS's quality audit runs in three rounds, each with a different focus:

Round One: Basic Functionality Check

Ensuring each website's core functionality works properly:

  • Page loading — Every page loads within 5 seconds with an HTTP 200 status code

  • Image integrity — All images load correctly with no broken images or missing alt text

  • Link validity — All internal and external links are valid with no 404 errors

  • JavaScript errors — No red error messages in the console

  • SSL certificates — HTTPS works correctly with no mixed content warnings

Round Two: Mobile Device Compatibility

Using Playwright to simulate phone and tablet devices:

  • Horizontal overflow — Whether the page width exceeds the screen, causing horizontal scrollbars

  • Font readability — Whether text is readable on mobile without zooming in

  • Touch targets — Whether buttons and links are large enough with sufficient spacing to avoid mis-taps

  • Language switching — Whether language toggle buttons work correctly on mobile

Round Three: Regression Testing

After fixing issues found in the first two rounds, we run the full test suite again:

  • Confirming all issues have been resolved

  • Verifying the fixes didn't introduce new problems

  • Generating the final quality report

3. Real-World Data: Audit Results for 100 Websites

Here are the results from HEY!BOSS's most recent batch of 100 brand websites:

  • Round one results — 23 issues found: 12 incorrect image paths, 8 CSS style inconsistencies, 3 JavaScript loading failures

  • Round two after fixes — 7 mobile device issues: 5 horizontal overflows, 2 buttons too small

  • Round three after fixes0 issues, all tests passed

Without automated testing, how many of these 30 issues would have been missed by manual testing? According to industry statistics, manual testing has a miss rate of about 15-25%. That means 5-8 issues could have gone live and been discovered by real users.

4. Automated Testing Goes Beyond Bug Finding

Playwright serves multiple purposes in HEY!BOSS's workflow beyond quality auditing:

  • Visual regression testing — Automatic screenshot comparison after every code change to ensure no unexpected UI changes

  • SEO checks — Automatically verifying meta tags, JSON-LD structured data, and Open Graph tags on every page

  • Performance monitoring — Running tests periodically to track page load time trends and alerting when speeds degrade

  • Deployment verification — Running a smoke test after every CI/CD deployment to confirm successful deployment

5. Why You Need Automated Testing Too

You might be thinking: "I'm not building 100 websites. I only have one company website. Do I really need automated testing?"

The answer is: yes. Because your website doesn't stay static after launch. Every time you update content, change product information, adjust prices, or publish a new article, something could accidentally break. Manual checks easily miss these issues, and by the time a customer reports "your website has a problem," you've already lost who knows how many potential clients.

Automated testing can be set to run daily — like hiring a 24/7 QA inspector for your website.

"Quality isn't something you check after the fact — it's something you build into the process from day one. Playwright is HEY!BOSS's secret weapon for quality assurance."

Conclusion

The era of manual testing is over. At the scale of AI-powered website building, automated testing isn't optional — it's essential. Playwright lets you guarantee quality with the speed and precision of code, whether it's 1 website or 100.

Top comments (0)