testing explanation

8/8/2019 Testing Explanation

1/22

SOFTWARE DEVELOPMENT LIFE CYCLESOFTWARE DEVELOPMENT LIFE CYCLE


2/22

TESTINGTESTING

Testing is nothing but finding the deviationsTesting is nothing but finding the deviations

of the application with according toof the application with according to

specificationsspecificationsThis is done in two ways those areThis is done in two ways those are

1).Manual testing1).Manual testing

2).Automation testing2).Automation testing


3/22

MANUAL TESTINGMANUAL TESTING**************************************************************************************************************


4/22

TestingTesting

----------------------

Testing is of three typesTesting is of three types

Black box testingBlack box testing White box testingWhite box testing

Grey box testingGrey box testing


5/22

Black box testingBlack box testing ::--Testing application withoutTesting application without

specific knowledge on platform and withoutspecific knowledge on platform and withoutchecking internal logic is called as black boxchecking internal logic is called as black box

testingtesting

White box testingWhite box testing ::-- Testing the application withTesting the application with

specific knowledge on platform and with checkingspecific knowledge on platform and with checking

internal logic is called as white box testinginternal logic is called as white box testing

Grey box testingGrey box testing ::--testing the application with thetesting the application with the

features of both black box & white box testingfeatures of both black box & white box testing


6/22

SOFTWARE PROCESSSOFTWARE PROCESS It is nothing but for developing every type ofIt is nothing but for developing every type of

software we have follow different approaches orsoftware we have follow different approaches or

methods which is called as software process.methods which is called as software process.

There care different type of software processThere care different type of software processmodels will be there those aremodels will be there those are

Waterfall modelWaterfall model

RAD modelRAD model Spiral modelSpiral model

Fish modelFish model

VV--modelmodel


7/22

WHITE BOX TESINGWHITE BOX TESING::--In this there will be twoIn this there will be two

types those aretypes those are

1)Unit testing1)Unit testing: Conducted by development team: Conducted by development teamAfter developing a single module they can checkAfter developing a single module they can check

the internal logic and loops and conditions e.t.c,forthe internal logic and loops and conditions e.t.c,for

this they use two techniques those arethis they use two techniques those are

a)Basis path testinga)Basis path testing

b)Operational testingb)Operational testing

TESTING TECHNIQUESTESTING TECHNIQUES


8/22

2)Integration testing2)Integration testing::--After completion of unitAfter completion of unit

testing on all small modules development teamtesting on all small modules development teamcombines all modules and forms as a big modulecombines all modules and forms as a big module

then they verifies wheather all modules arethen they verifies wheather all modules are

coordinating with each other properly or not iscoordinating with each other properly or not is

called as integration testingcalled as integration testing

For this there will be three techniquesFor this there will be three techniques

1)Top down approach1)Top down approach

2)Bottom up approach2)Bottom up approach

3)Hybrid approach3)Hybrid approach


9/22

TESTING TECHNIQUESTESTING TECHNIQUES

BLACK BOX TESTINGBLACK BOX TESTING ::--In this there will beIn this there will be

two types those aretwo types those are

1).1).Functionality testingFunctionality testing::--E

ighty percent of theE

ighty percent of thetesting process is occupied by this one only. Intesting process is occupied by this one only. In

this testing team verifies the application w.r.tothis testing team verifies the application w.r.to

requirements. For this we use number ofrequirements. For this we use number of

methods as followsmethods as follows


10/22

Functionality testing typesFunctionality testing types

CorrectnessCorrectness

Input domain testingInput domain testing

Error handlingError handling

Recovery testingRecovery testing

Configuration testingConfiguration testing

End to end (or) Inter system testingEnd to end (or) Inter system testing


11/22

System testingSystem testing::--Testing the application afterTesting the application afterfunctionality testing wheather it is workingfunctionality testing wheather it is workingin different aspects. For this there arein different aspects. For this there are

different techniques likedifferent techniques likePerformance:Performance:--Load, Stress, VolumeLoad, Stress, Volume

SecuritySecurity

UsabilityUsabilityUser interface testingUser interface testing

Manual support testingManual support testing


12/22

SOME OTHER TESTING TECHNIQUESSOME OTHER TESTING TECHNIQUES

Adhoc testingAdhoc testing Big bang testingBig bang testing

Incremental testingIncremental testing

Parallel testingParallel testing

Depth testingDepth testing

Breadth testingBreadth testing

Installation testingInstallation testing

Monkey testingMonkey testing

Universal testingUniversal testing


13/22

SOFTWARE TESING LIFE CYCLESOFTWARE TESING LIFE CYCLE

TEST INTIATIONTEST INTIATION

TEST PLANINGTEST PLANING

TEST DESIGNTEST DESIGN

TEST EXECUITIONTEST EXECUITION

TEST REPORTTEST REPORT

TEST EXECUITION CLOSURETEST EXECUITION CLOSURE


14/22

DEFECT/BUG LIFE CYCLEDEFECT/BUG LIFE CYCLE


15/22

AUTOMATION TESTINGAUTOMATION TESTING****************************************************************************


16/22

Benefits of automationBenefits of automation

Faster ExecutionFaster Execution

runs tests faster then human usersruns tests faster then human users

ReliableReliable

perform precisely the same operations each time they areperform precisely the same operations each time they arerunrun

RepeatableRepeatable

We can test how the AUT reacts after repeated executionWe can test how the AUT reacts after repeated execution

of the same operationsof the same operations ReusabilityReusability

reuse tests on different versions ofApplicationreuse tests on different versions ofApplication

Formalized processFormalized process


17/22

Guidelines for selecting the app for AutomationGuidelines for selecting the app for Automation

Business Critical ApplicationBusiness Critical Application

High Frequency usage of ApplicationHigh Frequency usage of Application

Repetitive TestingRepetitive Testing

Automation of GlobalAutomation of Global\\Localized ApplicationLocalized Application Multiple Platform usageMultiple Platform usage

ReusabilityReusability

PerformancePerformance


18/22

No to be automatedNo to be automated

Application having a short spanApplication having a short span

Control of External DevicesControl of External Devices -- A person may be neededA person may be needed

physically to control them into the states needed for testsphysically to control them into the states needed for tests


19/22

Applicability to Test TypesApplicability to Test Types

System TestingSystem Testing

System tests are the tests performed based on theSystem tests are the tests performed based on theoverall requirements of the system (typically businessoverall requirements of the system (typically businessflows). System testing can be automated toflows). System testing can be automated to

Cover the combined parts of the system.Cover the combined parts of the system.Verify the Functional performance includingVerify the Functional performance including

transaction flows, functional boundaries.transaction flows, functional boundaries.

Verify the end to end test scenarios.Verify the end to end test scenarios.


20/22

Integration TestingIntegration Testing Integration tests are the tests performed byIntegration tests are the tests performed by

integrating more than one application to ensure theintegrating more than one application to ensure theexpected functionality when they get integratedexpected functionality when they get integratedtogether. Integration tests can be automated totogether. Integration tests can be automated to

Test the flow of data between all integrationTest the flow of data between all integrationpoints of the integrated systems.points of the integrated systems.

Perform the prePerform the pre--condition and postcondition and post--condition verifications.condition verifications.

Verify the end to end test scenarios afterVerify the end to end test scenarios afterintegrationintegration


21/22

Regression testingRegression testing

Regression tests are done to ensure continuousRegression tests are done to ensure continuousworking of the unmodified parts of the systemworking of the unmodified parts of the systemafter enhancements or fixes. Regression testsafter enhancements or fixes. Regression testscan be automated tocan be automated to

Locate errors.Locate errors.

Increase confidence in correctness.Increase confidence in correctness.Preserve quality.Preserve quality.

Ensure continued operations.Ensure continued operations.


22/22

Technical testingTechnical testing

The following types of testing can be automated asThe following types of testing can be automated as

part of technical testing.part of technical testing.

Performance testingPerformance testing

Volume testingVolume testing

Stress testingStress testing

testing explanation

Documents