QA Agent Pro

About

QA Agent Pro is a platform for website QA testing and audits. The system detects most bugs using its own algorithms and AI agents. It also provides recommendations for improving the website.
The goal of the product is to automate website QA audits and provide structured reports that help product teams quickly identify UX, technical, and accessibility issues.

The Challenge

This project was an MVP created in a short timeframe to test the product idea.
At the start we only had an abstract product description and a rough vision of the final output for the user.
There was also no clear understanding of how the report table should look, which data should be displayed, or how the information should be structured into categories. Defining this structure was part of my responsibility.

Role & Responsibilities

My responsibilities included researching and creating a UX audit checklist for websites across different categories.
I also researched tools that could be used for real implementation of the audit logic.
Another part of my work was designing the UI and UX within a short timeframe and defining the structure of the content and reports.

Design Process & Approach

I researched the main competitors of the future product. I also reviewed various QA engineer reports to understand how audit data is typically structured and presented.
Before launching the main product, our team ran a Fake Door Test to validate the idea. During this stage we collected a list of websites from potential users. I audited these websites and used them to create the initial audit checklist.
Our main goal was to launch the first version of the product as quickly as possible. For this reason I decided to use a ready-made UI library to reduce design time and simplify further development.

UX Stage

UX development started with defining the main user journey and identifying potential problem areas for both users and developers.

Several interface iterations were created before the final structure was defined.

For the visual layer I used the Untitled UI library. The prototype was built directly using this design system without intermediate mid-fidelity wireframes.

One of the tasks was designing the bug report table structure.
At the beginning there was no clear understanding of what information should be included in the report and how it should be structured.
After several iterations we defined the final table structure. The goal was to make the report easy to read for both developers and product teams.
The final structure includes the following fields:

– Issue ID
– Description
– Severity (Critical, Major, Minor, Recommendation)
– Environment
– Steps to Reproduce
– Expected Result

The structured audit checklist made it possible to standardize the QA process for multiple website categories. It also helped define the data structure for automated scanning and reporting.

Once the main flow and functionality were defined, all edge cases, empty states, and error states were designed.

Handoff & Development Support

The design files were prepared for developer handoff. All component states were documented. Functional behavior was described. Error scenarios and edge cases were included.
During development I continued supporting the team. I reviewed usability and checked the correctness of the design implementation.

Outcome

I developed a UX audit checklist for small and medium business websites. The checklist covers e-commerce websites, landing pages, corporate websites, and service platforms.
Within a short timeframe I designed the product interface from scratch and defined a report table structure that meets both user needs and current technical constraints.
The product is currently in pre-release testing and is preparing for launch.