project

Quantello Test Automation

Automating test execution and analysis with speed, accuracy, and clarity.

Role
Lead UI/UX Designer
Tools
Figma, Illustrator, Photoshop
Context
Quantello Technologies
Deliverables
QA Suite & Dashboards
Quantello Cover
Overview

Project Overview

Quantello Test Automation Framework is a web-based platform that streamlines test case execution, result analysis, and client management for QA teams.

The system allows QA engineers to:

  • Upload test cases via Excel (.xlsx) or JSON (.json).
  • Run automated testing across multiple levels — Unit, Widget, and Integration.
  • View real-time test results in cards and detailed tables (Test ID, Input, Expected Output, Result, Time, Error).
  • Maintain a comprehensive history of all past test runs for traceability.
  • Manage multiple clients, assigning test cases to different projects or organizations.
  • Track their own performance through a personal profile dashboard with statistics.

This project aimed to build a centralized, easy-to-use test automation dashboard that reduces manual effort, minimizes errors, and empowers QA teams with actionable insights.

Project cover
The Problem

The Problem

Quality Assurance (QA) teams often struggle with disconnected tools and manual processes for managing test cases. Key challenges included:

These gaps resulted in wasted time, inconsistent testing, and unreliable reporting, making it difficult for QA teams to scale effectively.



The Goal

The Quantello Test Automation Framework was designed to:

Process

Process & Key UX Decisions

Designing Quantello required creating a clear, structured workflow for QA engineers, while also addressing multi-client complexity and ensuring scalability. Below are the major UX decisions:

File Upload & Validation
  • Supported Excel (.xlsx) and JSON (.json) formats for flexibility.
  • Drag-and-drop and browse options for easy upload.
  • Real-time validation with error states for unsupported formats or oversized files.

Why: QA engineers often work with different test formats; supporting both prevents blockers and ensures inclusivity.

Automated Categorization
  • Automatically sorted uploaded test cases into Unit, Widget, and Integration levels.
  • Displayed case count and file details immediately after upload.

Why: Reduced manual tagging effort and enforced standardization across all test runs.

Client Selection & Management
  • Users could assign uploaded test cases to an existing client or add a new client on the spot.
  • Designed a dedicated client management module with details (industry, contacts, logo, test history).

Why: Agencies often serve multiple clients; keeping tests organized per client improves clarity and accountability.

Running Tests & Real-Time Feedback
  • Tests ran across three levels (Unit, Widget, Integration).
  • Execution warnings alerted users that starting a new test would cancel an ongoing one.
  • Live progress indicators minimized confusion during execution.

Why: Running large test sets can take time; feedback loops and warnings prevent errors and wasted effort.

Results Visualization
  • Summary cards showed quick stats: Passed, Failed, Total Cases, Execution Time.
  • Detailed tables displayed: Test ID, Input, Expected Output, Actual Result, Error messages, Execution time in ms.
  • Export option for results.

Why: QA engineers need both at-a-glance success rates and deep debugging data in one place.

Test History
  • Centralized log of all test runs, categorized by client, file name, run date, and outcome.
  • Status indicators (Completed, Cancelled) for transparency.

Why: Historical visibility enables traceability, comparisons, and accountability in QA reporting.

Profile & Performance Dashboard
  • Profile section with personal stats: total tests run, passed, failed, and clients managed.
  • Editable profile details (name, contact, role, department).

Why: Helps QA engineers track personal contributions and provides transparency for managers.

Impact

Impact & Learnings

Impact
  • Delivered a centralized automation dashboard that reduced manual effort in test execution.
  • Standardized test categorization (Unit, Widget, Integration), improving consistency across teams.
  • Enabled multi-client management, making the tool suitable for QA agencies and large organizations.
  • Provided real-time feedback and detailed results, cutting down debugging time.
  • Improved transparency with complete test history and exportable reports.
  • Empowered QA engineers with personal performance insights through profile statistics.
Learnings
  • Designing for QA engineers emphasized the importance of speed and accuracy in workflows. Even small delays or unclear states caused frustration.
  • The need for flexible file formats (Excel, JSON) taught me how supporting multiple user entry points can reduce friction.
  • Balancing overview dashboards (cards, percentages) with deep details (tables, errors, execution times) was key to usability.
  • Working on multi-client workflows highlighted how information hierarchy and traceability are critical for enterprise-scale tools.
  • Personally, this project sharpened my skills in enterprise dashboard design and structuring complex technical data into clear UI patterns.
Download Case Study PDF ↗
Next Case Study

Holona Pet Care