Difference Between

Test Scenarios and Test

case
Test Scenarios Test Case
it is a high level documentation it is a detailed documentation

it tells what to test it tells how to test

it is derived from the requirement it is derived from test scenario

it require less time to write it require more time to write it

required less resource to write and execute required more resource to write and execute
compared with test case
the test scenario does not have data that you the test case have exact data that you need to
need to enter to test an application enter to test an application
Difference between Positive and Negative
Testing
 Positive testing Negative testing

testing the application by giving valid data testing the application by giving invalid data

it is performed as per the requirements it is not performed as per the requirements

it is performed first before negative testing it is performed after positive testing

anyone can do this professional can do this

it requires less time it requires more time

Difference between Functional and Non
Functional Testing
 Functional testing Non functional testing

it is based on the customer requirement it is based on the customer expectation

it describes what the product does it describes how the product works

it is performed before non functional testing it is performed after the functional testing

it is carried out using functional specification it is carried out using performance specification

it is easy to define the functional requirements it is difficult to define the non functional
requirements
Difference between Severity and Priority
 Severity
Impact of the bug on the customer business
workflow
it is categorized as
*blocker ,*critical,*major,*minor
severity indicates the seriousness of defect on
product functionality
it is associated with functionality
severity status is based on technical aspect of the
product
Priority
the order in which the developer should resolve
defect
it is categorized as *high,*low,*medium
priority indicates how soon the bug should be
fixed
it is associated with scheduling
priority status is based on customer requirement
Difference between Stub and Driver
 Stubs Drivers
stubs are used in top-down integration testing drivers are used in bottom-up integration
testing
stubs are basically known as a called programs stubs are basically known as a calling programs

dummy program for lower level components dummy program for higher level components

stubs are basically used in the unavailability of drivers are basically used in the unavailability of
low level modules high level modules
Difference between White box and Black
box Testing
 White box testing Black box testing
checking each and every line of the program testing the functionality of an application in
accordance with CRS

it is done by development team it is done by testing team

source code is visible source code is not visible

we need to know programing we need not know programing

we need to know internal design of programing we need not know internal design of programing
Difference between Alpha and Beta
Testing
 Alpha testing Beta testing
it is done by tester who are the internal it is done by clients or user who are not the
employee of same organization employee of same organization
it is performed at the dev site it is performed at the client location

it involves both white box and black box testing it involves only black box testing

it requires lab environment it don't requires lab environment

long execution cycle may be required for alpha only few weeks of execution cycle may be
testing required for beta testing
it is performed in virtual environment it is performed in real time environment

it is not open to the market and public it is open to the market and public

it is conducted for software application it is conducted for software product

Difference between Smoke and Sanity
Testing
 Smoke testing Sanity testing
testing the basic and critical feature of an it is a type of testing done after getting a build
application before rigorous testing with minor changes in code or functionality

it is performed by testers and developers it is performed only by testers

it is the subset of acceptance testing it is the subset of regression testing

it is usually documented and scripted it is usually not documented and unscripted

it is a general health checkup of product it is a specialized health checkup of product

exercise entire system from end to end exercise only particular component of entire
system
Difference between Regression and Re-
testing
 Regression testing
testing unchanged feature of an application to
make sure that it is not broken because of
changes
it is carried out parallel with retesting
Retesting
verifying whether the bug is fixed or not
it is carried out before regression testing

defect verification is not a part of regression defect verification is a part of regression testing
testing

it is done for passed test cases it is done for failed test cases

you can automate test case for regression testing you cannot automate test case for retesting
Difference between Manual and
Automation Testing
 Manual testing Automation testing
process of testing the software manually for testing the software using automation tool
finding defect is called manual testing without human intervention is called automation
testing
it is less efficient it is more efficient

it is less reliable it is more reliable

it requires more time for test execution it requires less time for test execution

investment cost is less investment cost is more

it is suitable for almost any software product it is suitable for only the stable systems
Difference between Static and Dynamic
Testing
 Static testing Dynamic testing

it is performed at the early stage of software it is performed at the later stage of software
development life cycle development life cycle

it is performed before code deployment

it is performed after code deployment
it involves walkthroughs ,code review, inspection it involves functional and nonfunctional testing
etc

static testing prevents defects dynamic testing find the defects

it takes less time

it takes more time
it is less costly it is highly costly
Difference between SDLC and STLC
 SDLC
STLC
it stands for software development life cycle
it stands for software testing life cycle
standard procedure for develop new software
standard procedure for test new software
it covers entire life cycle of software
it is limited for only for testing phase
it involves 7 stages
it involves 8 stages
SDLC requires more number of members
STLC requires less number of members
it helps to develop good quality software
it helps in making the software defect free
SDLC phases are completed before STLC phases
STLC phases are completed after SDLC phases
Difference between QA and QC
 Quality Assurance Quality Control
set of activities for ensuring the quality in the set of activities for ensuring the quality in the
process product

example verification example validation

it is process oriented it is product oriented

it is the proactive quality process it is the reactive quality process

aim of QA is prevention of defects aim of QC is detection of defects

everyone's responsibility testing team responsibility

Difference between Verification and
Validation
 Verification Validation
verifying the CRS,SRS,HLD and LLD is called testing the functionality of an application by
verification executing test cases is called validation

it comes before validation it comes after verification

it ensures that am I building product right it ensures that am I building right product

it does not involves execution of codes it always involves execution of codes

it is human based checking documents and files it is computer based execution of programs

uses walkthrough for verification uses the white box ,black box testing for validation