One Dashboard to Rule Them All: How Our QA Team Stopped Hunting Test Results Across Slack Links
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Trendyol's QA team built a unified internal dashboard to replace fragmented test result hunting across Slack notifications. Using Java 21, Spring Boot 3.3, Thymeleaf, and HTMX — with GitLab API integration and Allure/Karate/Cucumber reports — they created a single URL showing pipeline health across all microservices. An AI assistant helped generate the frontend despite no dedicated frontend team. Results: daily status checks dropped from ~15 minutes to under 2 minutes per engineer, standups shortened, 100% QA adoption within a month, 60% backend developer adoption, and ~30% faster flaky test resolution.
Table of contents
The Challenge: Navigating Fragmented Test ResultsThe Solution: A Pragmatic Tech StackGet Tuğçe Akın’s stories in your inboxDesigning the Unified View1. The Bird’s-Eye Overview2. Deep-Dive Reports3. Project-Based Statistics and Recent Runs4. Pipeline Activity and HeatmapsReal-World Impact and MetricsHow We Shipped the UI (The AI Co-Pilot)Conclusion25K Impressions1 Comment