QoalA

• 

  New UI

• 

  What it checks

• 

  Before Clean Up, review using browser-use

• 

  Before Clean Up, Additional review

• 

  Editing process

• 

  Browser-Use hard at work.

• 

  Alternative costs and time, we are cheaper

• 

  After Clean Up To Do

• 

  After Clean Up Share

• 

  After Clean Up Score

Inspiration: I wanted a way to automatically test websites for performance, accessibility, and quality without needing a manual QA team.

What it does: QoalA runs automated tests on websites using Browser-Use and Daytona to find issues with speed, accessibility, errors, design, and SEO. It tests the following: • Performance and loading speed • Accessibility compliance • Console errors and network issues • User interaction testing • Responsive design verification • SEO optimization

How we built it: I connected Browser-Use for automated browsing with Daytona for isolated testing environments and added tools like Lighthouse and Axe for detailed reports.

Challenges I ran into: It was difficult to sync Browser-Use with Daytona, handle false positives in automated tests, and make results consistent across browsers.

Accomplishments that I'm proud of: We built a working system that can test websites automatically and provide clear reports developers can use right away.

What we learned: Automation is powerful for QA, but the results need to be explained in simple and useful ways for developers.

What's next for QoalA: I need to plan to add automatic fix suggestions, a dashboard for results, and integrations with GitHub and Slack.

Built With

• browser-use
• cursor
• daytona