Objective Assessment of Software Product Quality
summary
Describes turning automated tests into an objective, 0–1 quality metric by using a weighted test plan and parsers that merge reports into a dashboard. Uses Selenium and Xcode test runners, unit and integration tests, test reviews and CI runs; gives concrete numbers (e.g. 500 scenarios ≈40 hours per platform → 320 hours across platforms; examples of 100k unit + 10k integration tests run on 50 machines). The resulting metric is used for management release decisions and printing readiness reports.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:26Software development problems
- 7:59Legacy code impact
- 10:48Management unawareness
- 12:35Software quality definition
- 13:59Automated testing solution
- 18:09Quality data sources
- 19:59Standards and test plans
- 21:47Feature weights in quality
- 24:22Quality metrics benefits
- 25:29Q&A
- 37:29Quality criteria
related talks
31mMeasure it or it didnt happen
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
39mEffective Quality Assessment
28mGet a grip on your quality by using Quality Views
47mTangible Software Quality
43mTo Measure or Not to Measure? That Is the Question
14mEssential Metrics for the Quality Assurance
46mQA to QE: Scaling Quality with Ownership, Code, and Culture