UM API Quality Improvement Results

Before-and-after comparison for Aqar API and UM API

13 August 2026 SonarQube
Test coverage after improvement
Aqar API
From 14.8% to
40%
UM API
From 5.5% to
83.4%
ACHIEVEMENT

A measurable quality transformation

Aqar API · Coverage +25.2 pp

Increased from 14.8% to 40.0%.

Aqar API · Duplication −90.3%

Reduced from 17.6% to 1.7%.

UM API · Coverage +77.9 pp

Increased from 5.5% to 83.4%.

UM API · Maintainability issues ≈94%

Reduced from approximately 1.5k to 92.

Headline result: UM closed three of four failed conditions. Security Hotspot review remains open, while Aqar coverage is still below the 76% target.
BASELINE

Aqar API — Before

BEFORE SonarQube screenshot of Aqar API before improvement
RESULT

Aqar API — After

AFTER SonarQube screenshot of Aqar API after improvement
MEASURED IMPACT

Impact on Aqar API

Test coverage

Before
14.8%
After
40.0%

Duplicated lines · 20% scale

Before
17.6%
After
1.7%
BASELINE

UM API — Before

BEFORE SonarQube screenshot of UM API before improvement
RESULT

UM API — After

AFTER SonarQube screenshot of UM API after improvement
MEASURED IMPACT

Impact on UM API

Test coverage

Before
5.5%
After
83.4%

Duplicated lines · 10% scale

Before
4.0%
After
1.0%
DELIVERY STORY

From a December target to one-sprint delivery

DEC

The original plan

Complete UM API automated test coverage by December 2026.

Year-end target
1×

AI-assisted sprint

AI accelerated test design, analysis, and iteration—moving coverage from 5.5% to 83.4% in one sprint.

76% target exceeded
+2

Same-month platform delivery

The team also integrated the ELK Stack and Redis during the same month.

Two parallel integrations
The achievement: a year-end quality milestone was delivered early while two major platform capabilities were added in parallel.
NCGR

Thank you

Aqar API and UM API quality improvement results