Siksha Sarovar

Siksha Sarovar (sikshasarovar.com) is a free educational web application that helps students in India learn programming and prepare for academic and competitive exams. The platform offers structured coding courses (C, C++, Python, Java, HTML, CSS, PHP, Power BI, AI, Machine Learning, Data Science), complete university curriculum notes for BCA/MCA students with previous year question papers, Class 10 and Class 12 CBSE/HBSE school notes, and dedicated preparation material for SSC, UPSC, Banking, Railway and other government exams. Browsing the site is completely free and requires no account. Users may optionally sign in with Google solely to save their learning progress, quiz scores and personal preferences across devices.

Privacy Policy | Terms of Service | Contact Siksha Sarovar | About Siksha Sarovar

v4.0.9 · PWA
Siksha Sarovar logo
Siksha Sarovar
Your Learning Universe

Siksha Sarovar is a free e-learning platform for coding courses, BCA university notes and competitive exam preparation. Optional Google sign-in saves your learning progress across devices.

Initializing knowledge base…
Compiling modules 0%

Unit 4.2: Test Management & Reporting

Lesson 16 of 16 in the free Software Testing notes on Siksha Sarovar, written by Rohit Jangra.

Unit 4.2: Test Management & Reporting

1. Test Management Infrastructure

Setting up the "Factory" for testing.

A. Test Infrastructure Management

  • Test Labs: Dedicated physical spaces with various devices (iPhones, Androids, Macbooks) for compatibility testing.
  • Virtual Environments: Using Docker/Kubernetes/VMware to spin up identical test servers in seconds. This prevents the "It works on my machine" excuse.
  • Test Data Management: You cannot test with empty databases. You need scripts to generate thousands of "Mock Users" or "Dummy Orders". Constraint: PII (Personal Identifiable Information) must be masked (GDPR compliance).

---

2. Configuration Management (CM)

Definition: Making sure everyone is testing the correct version of the software.

The Problem: Developer fixes a bug in v1.2, but Tester finds the bug still exists because they are testing v1.1.

The Solution: Strict version control (Git, SVN). Every build released to QA must have a unique tag (e.g., Build_2023_10_25_v1.0.5).

---

3. Defect Life Cycle (Bug Life Cycle)

The journey of a bug from discovery to closure.

  1. New: Tester finds a bug and logs it.
  2. Assigned: Test Lead assigns it to a Developer.
  3. Open: Developer accepts the bug and starts working.
  4. Fixed: Developer fixes cod and pushes to QA. Status becomes "Fixed".
  5. Retest: Tester verifies the fix.
  • If working: Status -> Verified/Closed.
  • If not working: Status -> Reopened.
  1. Rejected: Dev says "Not a bug" (Feature, Duplicate, or Works as Designed).
  2. Deferred: "Valid bug, but low priority. We will fix in next release."

---

4. Test Reporting & Metrics

How do we measure success? "We tested a lot" is not a metric.

Critical Metrics:

  1. Test Case Execution %: (Run / Total) * 100.
  • Goal: Should be 100% by end of cycle.
  1. Pass/Fail %: (Passed / Run) * 100.
  2. Defect Density: (Number of Defects / Size of Module).
  • Insight: Which module is the "buggiest"? (Defect Clustering).
  1. Defect Leakage: (Bugs found by User in Prod / Total Bugs) * 100.
  • Meaning: How many bugs "leaked" past QA? High leakage = Bad Testing.
  1. Defect Severity Index: Weighted average of bug severity. Are we finding mostly typos (Low) or crashes (Critical)?

Reports:

  • Daily Status Report: "Today we ran 50 tests. 45 Passed. 5 Failed. 2 Blockers."
  • Test Closure Report: The final summary. "We recommend releasing the product because Exit Criteria are met." OR "We do not recommend release due to open Critical defects."