Testing Training

7/31/2019 Testing Training

1/16

1

Software Testing


2/16

2

WHAT IS SOFTWARE TESTING?

Software testing is a process of verifying and validating that a softwareapplication or program.

1. Meets the business and technical requirements that guided itsdesign and development

2. Works as expected

PURPOSE

verification validation defectfinding


3/16

3

Typical Software Testing Process

1-Requirement Analysis:Software Requirement Specification(SRS)

Functional Specification

Designed Documents

Use case Documents

All the above documents are prepared by PM, TL and Dev teams itself withmeetings with client or Client itself.

2- Test Planning:

What to test first

Technologies to be used

who will test and whatMethodologies to be used

Whether it is manual or automated (If

automated then what to be automated)

Risk management

Which bug tracking tools to be used. etc


4/16

4

3- Test environment setup: In this phase of software testing we setupthe test environment in which we have to test the application.

Setup the test environment may include--------

Network Configuration

Software and hardware installation.

Meetings with vender's

Internet service provider may be the crucial part for for any S/w development

Organization.

4-Test Design: writing the test cases (Manual process)

writing test script (Automation process)

5-Test execution :In this phase we execute the test cases . We also runtest script (if applicable) to execute these test cases with the help of automation

tools.


5/16

5

6-Defect tracking and report: Inthis phase we track the defects .

through xls sheet. Mantis

Bugzilla

Zira

Quality Center

7- Test report: finally, testing team prepare following documents Test summary report

build release notes

note on what is covered and what to cover in next release.

Review acceptance. It may be the release note's mail reply from client


6/16

6

Software Development Life Cycle (SDLC)

It is overall process of developing information system through multi step processfrom investigation of initial requirements.


7/167

Types of SDLC: Waterfall model

V model

Spiral model

Prototype model

Rapid application Dev model

Agile Methodology

1.Waterfall Model:


8/168

Waterfall Strengths:

Easy to understand, easy to use

Provides structure to inexperienced staff

Sets requirements stability

Works well when quality is more important than cost or schedule

Waterfall Deficiencies:

All requirements must be known upfront

Little opportunity for customer to preview the system (until it may be too late)

When to use the Waterfall Model:

Requirements are very well known

Product definition is stable

Technology is understood

New version of an existing product


9/169

2.V-Shaped SDLC Model:


10/1610

Requirementsanalysis

Testplanning

Test

development

Test

execution

Test

reporting

Test result

analysis

Defect

Retesting

Regression

testing

Test Closure

Testing Life Cycle


11/1611

Bug Life Cycle


12/1612

Types of Testing

Based on knowledge of system : Black Box /Behavioral/Manual testing

White Box/Glass box/Automation Testing

Grey Box

Based on SDLC : Unit Testing

Integration Testing

System Testing

User Acceptance Testing

Based on purpose :

Functional Testing (Installation,Regression, Upgrade and backward compability testing)

Non Functional Testing (Performance, Load and Stress, Security)


13/1613

Some Other Types of testing

Smoke & Sanity Testing Regression & Re-Testing

Load & stress Testing

Alpha & Beta Testing

Monkey & Ad hoc Testing


14/16

14

Fields in the Bug Report

Bug No. Program/Module being tested

Version & release no.

Problem summary

Severity/priority

Environment

Detail Description of Bug

Steps to Reproduce

Reported by

Status Priority


15/16

15

The Cost of Bugs

Specification Design Code

Time When Bug Is Found

Cost


16/16

Testing Training

Documents

Transcript of Testing Training