Content of Test Design Document

AI Summary

An AI-generated summary of this video lecture.

This lecture provides a detailed breakdown of the Test Design Document (TDD) structure and the phases of software testing. The instructor begins by outlining the Introduction section of the TDD, covering Purpose and Scope, and explains how it references external documents like the SRS and SDS. The session progresses to the Test Plan, defining its core components: scope, approach, resources, and schedule. The instructor then details the Recording of Tests and Reporting Test Results, emphasizing the documentation of failures and corrections. Finally, the lecture distinguishes between Verification Testing (Unit, Integration) and Validation Testing (System, Acceptance), clarifying the specific goals and timing of each phase in the software development lifecycle.

Chapters

1. 0:00 – 2:00 00:00-02:00

   The lecture begins by introducing the **Test Design Document (TDD)** structure. The instructor highlights the **Introduction** section, breaking it down into **Purpose** and **Scope**. She writes "Format" and "Section" next to a document icon to illustrate the document's organization. The **Purpose** is defined as clearly stating the document's intent and intended audience, while the **Scope** provides an overview of the testing process and major phases. She underlines "major phases of the testing process" in the text to emphasize the need for a high-level view of the testing strategy.

2. 2:00 – 5:00 02:00-05:00

   The instructor elaborates on the **Scope**, noting it specifies "What to test" and what is excluded, such as third-party software. She then introduces the **Glossary** section, which defines technical terms used in the document. Moving to **References**, she explains that external documents like the **System Requirement Specification (SRS)** and **System Design Specification (SDS)** are cited. She draws a diagram showing SRS and SDS pointing to the TDD, indicating their relationship. She underlines "System Requirement Specification" and "System Design Specification" to show their importance as reference points.

3. 5:00 – 10:00 05:00-10:00

   The lecture covers the **Overview of Document**, describing its contents and organization (chapters/sections). The focus shifts to **2. Test Plan**, defined as a document describing the scope, approach, resources, and schedule of testing activities. The instructor underlines these four key terms. She explains that the plan identifies test items, features, tasks, and the person responsible for each task. Handwritten notes include "Tester A", "Logic", and "Module" to exemplify task assignment. She writes "Scope, Approach, Schedule, Resource" below the definition to reinforce the key components.

4. 10:00 – 15:00 10:00-15:00

   Section **2.1 Schedules and Resources** is discussed, with the instructor writing specific dates like "24th Jan" and "31st Jan" to illustrate a testing schedule in phases. Next, **2.2 Recording of Tests** is explained. This section specifies the format for recording results, including the item tested, the tester, reference data, expected results, and the date. If a test fails, the person responsible for correction is documented. Handwritten notes show "Documenting", "Test -> Record process -> format document". She underlines "item to be tested", "person who did the testing", "results expected" to highlight critical data points.

5. 15:00 – 20:00 15:00-20:00

   The instructor discusses **2.3 Reporting Test Results**, which summarizes successful tests and errors to be rectified. She draws a box listing "Successful", "Failed", "Bugs/Defects Exist", and "Issue -> Fixed". The lecture then moves to **3. Verification Testing**, noting it relates to [SRS & SDS]. **3.1 Unit Testing** ensures accurate functioning of a unit, while **3.2 Integration Testing** is done on modules or sub-systems. She writes "Before deliver" to indicate timing. She underlines "accurate functioning of that unit" to stress the goal of unit testing.

6. 20:00 – 20:52 20:00-20:52

   The final section covers **4. Validation Testing**, where the instructor writes "Actual expected". **4.1 System Testing** is described as the top level of integration testing, validating requirements as described in the SRS. **4.2 Acceptance and Beta Testing** involves real data used by the development team (alpha) or the customer (beta). The text highlights that results are reported back and handled by developers. She highlights the text "real data is used for testing by the development team" to distinguish between internal and external testing phases.

The lecture provides a comprehensive guide to software testing documentation and execution. It begins with the structural components of a Test Design Document, emphasizing the importance of defining purpose, scope, and references to SRS/SDS. It then transitions into the Test Plan, detailing the logistical aspects like schedules, resources, and task assignment. The recording and reporting phases are crucial for tracking progress and managing defects. Finally, the distinction between Verification (checking against specs) and Validation (checking against user needs) is clarified through the breakdown of Unit, Integration, System, and Acceptance testing. This flow ensures a systematic approach from planning to final delivery.