The article explains why testing is essential in software development and introduces ten widely used defect metrics—such as defect density, arrival rate, fix rate, effectiveness, severity, reopen rate, escape rate, average fix time, type distribution, and convergence trend—to help teams assess and improve product quality.
This article presents a detailed framework for quality and testing service SLAs, outlining standard chapters, service items, performance metrics, response times, quality commitments, calculation methods, and ownership responsibilities across data collection, test efficiency, performance monitoring, and quality tracking.
At the 2021 China Internet Test Development Conference, ZTO Technology’s senior architect Gong Linhua detailed how their thousand‑person team builds a robust quality assurance system through business testing, continuous innovation, specialized training, and precise metric‑driven management, aiming to accelerate delivery while maintaining high software quality.
This guide explains how to evaluate the return on investment of Selenium‑based cross‑browser test automation by defining key metrics, outlining calculation formulas, discussing common pitfalls, and offering practical steps to maximize efficiency, coverage, and risk reduction.
This article introduces the architecture of smart speaker voice interaction systems, covering wake‑word activation, automatic speech recognition (ASR), natural language understanding (NLU), skill processing, text‑to‑speech synthesis (TTS), and the key performance and testing metrics for each component.
This article examines common software testing antipatterns, explains why testing the wrong functionality and over‑focusing on code coverage are misguided, introduces a mental model for prioritizing critical, core, and other code, and presents practical metrics and guidelines for effective, behavior‑driven testing.
This article expands on common software testing antipatterns, explaining why testing the wrong functionality, focusing on internal implementation, and obsessing over code‑coverage percentages can waste effort, and it introduces a mental model, practical metrics, and guidelines for writing effective, business‑oriented tests.
