Mt s4 types

DO NOT DISTRIBUTE – HIGHLY CONFIDENTIAL

Agenda:

• Testing Types


Types of Testing:

Two Types of Testing

• Static Testing

• Dynamic Testing

2 www.talentsprint.com


Static Testing:

• Verifying are we implementing the right system or

not is called static testing.

• A form of verification that most of the times does

not requires execution of software.

• It is also called Verification Process.

• Static testing will be carried out with the help of

Reviews.



Review:

• Examining a project related work or a platform

related work is called Review.

• Eg: Examining requirements i.e. BRS, SRS, Design

documents and code etc is called Review.

• Note: Static testing does not execute the code.



Types of Reviews:

– Management reviews

– Technical reviews

– Code reviews

– Formal reviews(inspections and audits)

– Informal reviews(peer reviews)



Management Review:

– These reviews will be conducted by middle level and high

level management to monitor status.

– i.e. weather all activities are going as per this plan effort or

not. These reviews are helpful to take the necessary

corrective actions if there are any slip pages.

– Slippage: Deviation between planned efforts to actual

effort is called slippage.

– Note: Daily/ weekly project status meetings are called

management reviews.



Technical Review:

– These reviews will be conducted among technical

members such as design teams or developers or testers

to decide the best approach of implementing a job if

there are any questions while implementing a technical

work.

Code Review:

– These reviews will be conducted among developers on

the source code to confirm the coding standards.



Formal Reviews:

– If any review conducted with a pre-plan and by following a

set of pre-defined procedures and documentation then

these reviews are called formal reviews.

– The five procedural roles are:

Author

Moderator

Reader

Recorder and

Inspector.



Procedural Roles of Formal Reviews:

• Author: A person who prepared a document.

• Moderator/Inspection leader: A main person who is

responsible for review activities.

• Reviewers/Inspectors: Participants of a review activity.

• Scribe/Recorder: A person who records defects during review

meeting.

• Note: Inspections and Audits are the best examples for

Formal Reviews.



Phases of Formal Reviews:

– Planning

– Kick of Meeting

– Preparation

– Review Meeting

– Rework

– Follow up



Inspection:

– If a formal review is conducted while executing a task then it is

called Inspection.

– Checking of a software product (or part of a product) with the

intention of:

Locating defects.

Confirming traceability of relevant requirements.

Checking for conformance to relevant standards and

conventions.



Inspection:

– The fundamental goal of the inspection process is to eliminate

defects from a given, well defined work product.

– The inspection team is a group of individuals that work together

to analyze each work product of a development activity in order

to detect and remove defects.

– Inspections accomplish this by assigning five different

procedural roles to the individuals that make up the team

– The five procedural roles are: Author, Moderator, Reader,

Recorder, and Inspector.



Audits:

– If a formal review is conducted after completion

of a task to confirm does the task is accomplish as

per the pre-defined check list or not, then it is

called audit.



Informal Reviews:

– If a formal review is conducted without following

predefined procedures, then these reviews are called

informal reviews.

– Peer Reviews & Walk Through are the best

examples of Informal Reviews.



Informal Reviews:

Peer-reviews:

– The reviews conducted among colleagues are called

peer reviews.

Walk-throws:

– Training session’s i.e. knowledge transfer sessions are

called walk-throws.



Informal Reviews:

Walk-throws:

– An informal process, initiated by the author of a software

product to a colleague for assistance in locating defects and for

suggesting improvements.

Normally not planned.

Author explains the product.

Colleague comes out with observations.

Author provides clarification if required.

Author notes down relevant points and takes corrective

actions.



Types of Testing:

Objectives of Reviews:

Reviews are helpful to determine the following.

To determine defects in requirements.

To find defects in design.

To identify deviations in coding standards and to

improve the process.



Types of Testing:

Dynamic Testing:

– Validating the source code and validating the application to

confirm does the code and the application are working as

expected or not is called validation.

– Validating whether the developed system is right or not.

– It is called Dynamic Testing.

White box testing

Black box testing

Grey box testing



Summary:

In this topic we have learnt:

1. Static Testing

Verification and it techniques.

2. Dynamic Testing

Validation and it techniques.



Review Questions:

1. Why do you use verification techniques even though the Validation

techniques used?

a) Verification is better than Validation

b) Verification is a Black-box testing

c) Verification is helps in finding-out the defects earlier stages

d) Verification can be used instead of Validation.

2. Which of the Following Verification techniques is a team activity?

1.Reviews

2.Inspections

3.Walkthroughs

4.None of the above



Review Questions:

3.Match the Following:

a) Verification 1) BETA testing

b) Validation 2) Walkthroughs

c) Past-Mortem Reviews 3) System Testing

d) Completely Informal 4) Reviews

e) After ALPHA testing 5) Post-implementation Reviews


22

Question and Answer

Date post:	15-Apr-2017
Category:	Documents
Upload:	testinggeeks
View:	79 times
Download:	1 times

Mt s4 types

Documents