Mastering Test Activities Across the Software Development Lifecycle

Software Development Lifecycle Test Activities

1. Planning & Monitoring

1.1 Test Plan – Defining Business Goals

Understand requirements by analyzing product business goals, mandatory features, priorities, risk levels, and quality expectations.

1.1.2 Focus Points in Test Activities

1.2 Business Scenario Analysis

Test scenario analysis method: Requirement analysis → Business use‑case grooming → Use‑case specification → Test scenario.

1.3 Test Strategy in the Planning Phase

Answer two questions: what to test and how to test. Define test scope, objectives, focus areas, depth and breadth, activity scheduling, and test layering.

1.4 Data Collection

Collect quantitative process data (e.g., number of business use cases, scenarios, risk items, test cases) and progress data, establish baselines, and set coverage rules.

2. Analysis & Design

2.1 Test Analysis – Refining the Test Strategy

Break down the strategy into test‑plan, execution (depth‑first or breadth‑first), release, monitoring, and efficiency strategies. Ensure each business use case is covered by relevant quality attributes.

2.2 Test Design

2.2.1 Foundations of Test‑Case Design

Basic set theory concepts (sets, subsets, unions, intersections, complements) help guarantee completeness and avoid redundancy. Define partitions where every element belongs to exactly one subset.

Function concepts (domain, range) and logical operators are also essential.

2.2.2 Test‑Case Design Techniques

Equivalence class partitioning

Boundary‑value analysis

Decision tables (conditions, actions, rules)

State‑based modeling (finite‑state machines, Petri nets, state charts)

Coverage criteria: statement, branch, condition‑combination, path, all‑paths, and minimal linear‑independent coverage

Algorithm for minimal linear‑independent path count is illustrated below:

2.2.3 Test Data

Cover data‑flow aspects based on modeled scenarios.

2.2.4 Non‑Functional Extensions

Large‑data volume testing

Concurrent execution testing

Repeated parameter execution

Invalid input testing

3. Implementation & Execution

3.1 Integration Testing

Top‑down integration

Bottom‑up integration

Sandwich integration

Pairwise and adjacent integration based on call graphs

Path‑based integration

3.4 Acceptance Testing

Product Development (PD) must participate and produce results. Typical acceptance matrix includes requirement ID, description, quality attribute, verification status, test result, and responsible PD.

4. Evaluation & Reporting

4.1 Test Coverage Evaluation

Assess requirement coverage, code coverage, execution rate, pass rate, and defect density for each requirement and associated test cases.

4.2 Test Process Evaluation

Analyze test‑case effectiveness, testing methods, and resource investment (person‑days, roles, phases).

4.3 Defect Analysis

Classify defect severity (Blocker, Major, Normal, Trivial) and examine defect density, fix rate, trends, root causes, and introduction phases (requirements, design, coding, change, or fix).

5. Test Closure Activities

Project summary

Online business effect tracking

Online issue analysis

Failure analysis

Quality data operations