Verification Are we building the system

right i ht
It is the process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of the phase. (IEEE)

Verification is the process of evaluating, reviewing inspecting and doing checks on reviewing, work products. ` Verification is applied to all phases. phases ` Verification is called human testing
`

Validation - Are we building the right system

It is the process of evaluating a system or component during i or at the end of f the development process to determine whether it satisfies specified requirements.(IEEE) (IEEE) ` Validation involves executing the actual S/W. ` It is a computer based technique technique. ` More errors are explored.

Software Testing Life Cycle

A Test Case is a set of conditions or variables under which hi h a tester will ill determine d i whether h h an application li i or software system is working correctly. A Test Suite is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviors (known as a validation suite). suite) A Test Plan is a document detailing a systematic approach to testing a system such as a machine or f software. A Test Report has the documents what occurred when the test scripts were run.

Requirement q Analysis y is the process of analyzing

software for design and implementation methods and testable aspects are recorded Documents involved:
x Requirement Specification documents x Functional Specification documents x Design Specification documents (use cases, etc) x Use case Documents x Test Trace-ability Matrix for identifying Test Coverage

Test Planning defines the scope of the work to be performed / planned (people, (people cost, cost Efficiency etc.)
x Test Process Flow x Test Scope, Test Environment x Different Test p phase and Test Methodologies g x Manual and Automation Testing x Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc x Evaluation & identification Test, Defect tracking tools

Documents Involved:
x Master Test Plan Plan, Test Scenario Scenario, SCM

x A test plan is usually prepared by or with significant input from Test Engineers.

Questions to be answered:

How many tests are needed? How long will it take to develop those tests? How H l long will ill it i take k to execute those h tests? ? Test estimation Test development and informal validation Validation readiness review and formal validation Test completion criteria

Topics to be addressed:

Test Case Development

Process:
x Test Traceability Matrix and Test coverage x Test Scenarios Identification & Test Case preparation x Test T t data d t and d Test T t scripts i t preparation ti x Test case reviews and Approval x Base lining under nder Config Configuration ration Management

Documents Involved:
t Pl xT Test Plan, RTM x Test cases

Test Case Execution:

Process:
x x x x x x x x Executing i Test cases Testing Test Scripts C Capture, review i and d analyze l Test T Results R l Raising the defects and tracking for its closure Test Cases T i report Test E Execution Bug report R i Requirement t traceability t bilit matrix ti

Documents D t I Involved: l d

Test Results & Defects Reporting p g

Process:
x x x x Defect logging Assigning defect and fixing Retesting Defect closing

Documents involved:
x Test report x Bug Report

Test Closure (Product Delivery) Process: x After the product had undergone several tests, the acceptance test is done by the user/client i.e. UAT, wherein the use cases were executed and the product is accepted to go on live x Test Metrics and process Improvements made x Build release x Receiving acceptance Documents involved x Test summary reports x UAT Test Plan, UAT Test cases

A Traceability Matrix is a document, usually in the form of a table, that correlates any two base lined documents that require a many-to-many relationship to determine the completeness of the relationship.