SlideShare uma empresa Scribd logo
1 de 27
Baixar para ler offline
Types Of Testing
Presented By:
Sonam Agarwal
3ird year, IT
Introduction & Fundamentals
 What is Software Testing?
 Why testing is necessary?
 Who does the testing?
 What do we test?
Error ,Bug ,Fault ,Failure
 A person makes an Error That creates a fault in software
That can cause a failure in operation Bug, Fault & Failure.
 Error : An error is a human action that produces the
incorrect result.
 Bug : The presence of error at the time of execution of
the software.
 Fault : State of software caused by an error.
 Failure : Deviation of the software from its expected
result.
Objectives of testing
 The aim of the testing is to identify all defects existing
in a software product. It is not possible to guarantee
that the software is error free. This is because of the
fact that the input data domain of most software
products is very large.
 A good test case is one that has a high probability of
finding an as-yet-undiscovered error.
 A successful test is one that uncovers an as-yet-
undiscovered error.
 What testing cannot do ?
o Cannot show the absence of errors.
Objectives of a Software Tester
 Find bugs as early as possible and make sure they get
fixed.
 To understand the application well.
 Study the functionality in detail to find where the
bugs are likely to occur.
 Study the code to ensure that each and every line of
code is tested.
 Create test cases in such a way that testing is done to
uncover the hidden bugs and also ensure that the
software is usable and reliable.
Verification & Validation
 Verification - refers to the set of activities that ensure
that software correctly implements a specific
function.
 Validation- refers to a different set of activities that
ensure that the software that has been built is
traceable to customer requirements.
Verification: "Are we building the product right?"
Validation: "Are we building the right product?"
Testing Vs Debugging
 Debugging is not Testing.
 Debugging always occurs as a consequence of testing.
 Debugging attempts to find the cause of an error and
correct it.
When to Start Testing in SDLC
Phases of SDLC
 Feasibility Study
 Requirements Analysis and Specification
 Design
 Coding
 Testing
 Maintenance
Types Of Testing
White Box Testing Black Box Testing
System Testing
Usability Testing
Static Testing Dynamic Testing Performance Test
Walkthrough Unit Testing
Code Reviews Integration Testing
Code Inspection Regression Testing
White Box Testing
 The internals of software are tested to make sure that they
operate according to specification and design.
 Test cases are based on internal structure of software.
 Areas
Code Coverage ,Statement Coverage, Branch Coverage,
Condition Coverage ,Loop Coverage, Path Coverage ,Data Flow
Coverage.
• Techniques
o Flow graph testing ,Graph matrices ,Control structure testing ,
Data flow testing.
Static Testing
 Static testing of a program carried out without executing the
program.
 It aims to find defects in the software product in the early
stages of software development, so that they can be fixed
easily.
 It can find errors that occur on paths uncovered by testing
 It explores all possible execution paths in a program at compile
time.
 Who
o By a team of individuals.
o By individual who didn’t write the code.
Code Review
o A code review can be done as a special kind of inspection in
which the team examines a sample of code and fixes any
defects in it. In a code review, a defect is a block of code which
does not properly implement its requirements, which does not
function as the programmer intended.
o Are the variables name meaningful?
o Are the variables initialized?
o Are pointers initialized properly?
o Are there infinite loops?
o Has the usage of operators like = and == or & and && been
checked or not?
Code Inspection
 It is the most formal technique.
 The aim of this review type is to uncover defects in the
document in the early stages of software development
and thereby improve the quality of the product.
 An inspection is one of the most common review
practices found in software projects. In an inspection, a
work product is selected for review and a team is
gathered for an inspection meeting to review the work
product.
 The goal of the inspection is to identify defects.
Code Inspection(continued…)
The stages in the inspections process are:
Planning: The inspection is planned by the moderator.
Overview meeting: The author describes the background of the work product.
Preparation: Each inspector examines the work product to identify possible
defects.
Inspection meeting: During this meeting the reader reads through the work
product, part by part and the inspectors point out the defects for every part.
Rework: The author makes changes to the work product according to the
action plans from the inspection meeting.
Follow-up: The changes by the author are checked to make sure everything is
correct.
The process is ended by the moderator when it satisfies some predefined exit
criteria.
Unit Testing
 Objectives
The primary goal of unit testing is to take the smallest
module of testable software, and running it in isolation by
using prepared test cases and comparing with the actual
result to test the interfaces between modules.
 When
After modules are coded
 Who
Developer/programmer
 Methods
o White Box testing techniques
What are Stubs, Drivers ?
 A stub is a computer program which is used as a
substitute for the body of a software module or a dummy
module which simulates the function of a module called
by a given module under test.
 Driver a module which transmits test cases in the form of
input arguments to the given module under test and
either prints or interprets the results produced by it.
Integration Testing
 Objectives
To technically verify proper interfacing between modules,
and within sub-systems that satisfy functional
requirement.
 When
After modules are unit tested
 Who
Developers/Programmer
 Methods
o White Box techniques
o Black Box techniques
Types Of Integration Testing
 Top-Down Integration testing
 Bottom-Up Integration testing
Top Down Integration Testing
A
B
Stub
Stub
Stub
A
B
C
Stub
Stub
stub
Stub
Bottom Up Integration testing
Test
Drivers
Level N
Level N-1 Level N-1
Level NLevel N
Test
Drivers
Test
Drivers
Test
Drivers
Test
Drivers
Regression Testing
 Objectives
o It is used to checks faults, defects propagated to other
modules by changes made to existing program.
o This testing is used to reduce the side effects of changes.
o Testing is done by re-executing the previous versions of
the application.
 Who
Programmers or independent testers
Black Box Testing
 In the black-box testing approach, test cases are designed
using only the functional specification of the software, i.e.
without any knowledge of the internal structure of the
software.
 It explains the process of giving the input to the system
and checking the output, without considering how the
system generates the output. It is also known as
Behavioral Testing.
 It attempts to find error in the external behavior of the
code.
System Testing
 Objectives
The goal of system testing is not to find out faults but to
demonstrate performance.
 What
The system testing is actually a series of different tests ,
primary purpose of which is to fully exercise the system.
All work to verify that all system elements have been properly
integrated and perform allocated functions.
 When
After Integration Testing
 Who
Development Team
Acceptance Testing
 Objectives
To verify that the system meets the user requirements.
It is the system testing performed by the customer him/herself
after the product delivery to determine whether to accept or
reject the delivered product.
 When
After System Testing
 Who
Users / End Users
 Methods
o Black Box techniques
Alpha Testing
 It is a testing in which the version of complete software is
tested by the customer under the supervision of
developer.
 This testing is performed at the developer's site in a
control environment under the guidance of a developer.
Beta Testing
 It is a testing in which software is tested by a customer
without the developer being present.
 This testing is performing at the customer's site.
 Customer records the problems and reports it to the
developer then the developer makes appropriate
modifications.
Thank You

Mais conteúdo relacionado

Mais procurados (20)

Software testing
Software testingSoftware testing
Software testing
 
Testing methodology
Testing methodologyTesting methodology
Testing methodology
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
Software testing
Software testing Software testing
Software testing
 
Software Testing or Quality Assurance
Software Testing or Quality AssuranceSoftware Testing or Quality Assurance
Software Testing or Quality Assurance
 
Introduction to software testing
Introduction to software testingIntroduction to software testing
Introduction to software testing
 
Introduction & Manual Testing
Introduction & Manual TestingIntroduction & Manual Testing
Introduction & Manual Testing
 
Types of Software Testing
Types of Software TestingTypes of Software Testing
Types of Software Testing
 
Software Testing Introduction
Software Testing IntroductionSoftware Testing Introduction
Software Testing Introduction
 
Software testing methods, levels and types
Software testing methods, levels and typesSoftware testing methods, levels and types
Software testing methods, levels and types
 
Automated Testing vs Manual Testing
Automated Testing vs Manual TestingAutomated Testing vs Manual Testing
Automated Testing vs Manual Testing
 
Software testing ppt
Software testing pptSoftware testing ppt
Software testing ppt
 
Testing fundamentals
Testing fundamentalsTesting fundamentals
Testing fundamentals
 
Software Testing Process
Software Testing ProcessSoftware Testing Process
Software Testing Process
 
SOFTWARE TESTING
SOFTWARE TESTINGSOFTWARE TESTING
SOFTWARE TESTING
 
Software testing
Software testingSoftware testing
Software testing
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
Software Testing Fundamentals
Software Testing FundamentalsSoftware Testing Fundamentals
Software Testing Fundamentals
 
Types of software testing
Types of software testingTypes of software testing
Types of software testing
 
Software Testing
Software TestingSoftware Testing
Software Testing
 

Destaque

Test and some test types (ev elt)
Test and some test types (ev elt)Test and some test types (ev elt)
Test and some test types (ev elt)theryszard
 
Language Testing: Approaches and Techniques
Language Testing: Approaches and TechniquesLanguage Testing: Approaches and Techniques
Language Testing: Approaches and TechniquesMonica Angeles
 
Approaches to Language Testing
Approaches to Language TestingApproaches to Language Testing
Approaches to Language Testingmpazhou
 
Kinds of testing (2nd)
Kinds of testing (2nd)Kinds of testing (2nd)
Kinds of testing (2nd)Harry Subagyo
 
Principles of Language Assessment
Principles of Language AssessmentPrinciples of Language Assessment
Principles of Language AssessmentA Faiz
 

Destaque (12)

Types of tests and types of testing
Types of tests and types of testingTypes of tests and types of testing
Types of tests and types of testing
 
Test and some test types (ev elt)
Test and some test types (ev elt)Test and some test types (ev elt)
Test and some test types (ev elt)
 
Language Testing: Approaches and Techniques
Language Testing: Approaches and TechniquesLanguage Testing: Approaches and Techniques
Language Testing: Approaches and Techniques
 
Types of test
Types of testTypes of test
Types of test
 
Types of Test
Types of Test Types of Test
Types of Test
 
Approaches to Language Testing
Approaches to Language TestingApproaches to Language Testing
Approaches to Language Testing
 
Language Testing
Language TestingLanguage Testing
Language Testing
 
Types of Test
Types of TestTypes of Test
Types of Test
 
Approaches to language testing
Approaches to language testingApproaches to language testing
Approaches to language testing
 
Kinds of testing (2nd)
Kinds of testing (2nd)Kinds of testing (2nd)
Kinds of testing (2nd)
 
Type of Test
Type of TestType of Test
Type of Test
 
Principles of Language Assessment
Principles of Language AssessmentPrinciples of Language Assessment
Principles of Language Assessment
 

Semelhante a Types of testing

Semelhante a Types of testing (20)

Software Testing - A sneak preview By Srikanth
Software Testing - A sneak preview By SrikanthSoftware Testing - A sneak preview By Srikanth
Software Testing - A sneak preview By Srikanth
 
Software testing
Software testingSoftware testing
Software testing
 
Software testing
Software testingSoftware testing
Software testing
 
Software testing ppt
Software testing pptSoftware testing ppt
Software testing ppt
 
Software testing basic
Software testing basicSoftware testing basic
Software testing basic
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
Software testing sengu
Software testing  senguSoftware testing  sengu
Software testing sengu
 
Validation & verification software engineering
Validation & verification software engineeringValidation & verification software engineering
Validation & verification software engineering
 
Software testing
Software testingSoftware testing
Software testing
 
SOFTWARE TESTING
SOFTWARE TESTINGSOFTWARE TESTING
SOFTWARE TESTING
 
Software testing strategies
Software testing strategiesSoftware testing strategies
Software testing strategies
 
Abc of testing
Abc of testingAbc of testing
Abc of testing
 
SOFTWARE TESTING.pptx
SOFTWARE TESTING.pptxSOFTWARE TESTING.pptx
SOFTWARE TESTING.pptx
 
Software testing
Software testingSoftware testing
Software testing
 
White box & black box testing
White box & black box testingWhite box & black box testing
White box & black box testing
 
Software testing
Software testingSoftware testing
Software testing
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
S.t.
S.t.S.t.
S.t.
 
Introduction to software testing
Introduction to software testingIntroduction to software testing
Introduction to software testing
 
softwaretestingppt-FINAL-PPT-1
softwaretestingppt-FINAL-PPT-1softwaretestingppt-FINAL-PPT-1
softwaretestingppt-FINAL-PPT-1
 

Último

Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesMohammad Hassany
 
Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.EnglishCEIPdeSigeiro
 
The Singapore Teaching Practice document
The Singapore Teaching Practice documentThe Singapore Teaching Practice document
The Singapore Teaching Practice documentXsasf Sfdfasd
 
UKCGE Parental Leave Discussion March 2024
UKCGE Parental Leave Discussion March 2024UKCGE Parental Leave Discussion March 2024
UKCGE Parental Leave Discussion March 2024UKCGE
 
Diploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdfDiploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdfMohonDas
 
General views of Histopathology and step
General views of Histopathology and stepGeneral views of Histopathology and step
General views of Histopathology and stepobaje godwin sunday
 
How to Solve Singleton Error in the Odoo 17
How to Solve Singleton Error in the  Odoo 17How to Solve Singleton Error in the  Odoo 17
How to Solve Singleton Error in the Odoo 17Celine George
 
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdfMaximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdfTechSoup
 
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdfP4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdfYu Kanazawa / Osaka University
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...Nguyen Thanh Tu Collection
 
Education and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptxEducation and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptxraviapr7
 
How to Add a many2many Relational Field in Odoo 17
How to Add a many2many Relational Field in Odoo 17How to Add a many2many Relational Field in Odoo 17
How to Add a many2many Relational Field in Odoo 17Celine George
 
How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17Celine George
 
How to Show Error_Warning Messages in Odoo 17
How to Show Error_Warning Messages in Odoo 17How to Show Error_Warning Messages in Odoo 17
How to Show Error_Warning Messages in Odoo 17Celine George
 
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxPractical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxKatherine Villaluna
 
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxPISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxEduSkills OECD
 
How to Add Existing Field in One2Many Tree View in Odoo 17
How to Add Existing Field in One2Many Tree View in Odoo 17How to Add Existing Field in One2Many Tree View in Odoo 17
How to Add Existing Field in One2Many Tree View in Odoo 17Celine George
 
How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17Celine George
 
M-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptxM-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptxDr. Santhosh Kumar. N
 

Último (20)

Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming Classes
 
Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.Easter in the USA presentation by Chloe.
Easter in the USA presentation by Chloe.
 
The Singapore Teaching Practice document
The Singapore Teaching Practice documentThe Singapore Teaching Practice document
The Singapore Teaching Practice document
 
UKCGE Parental Leave Discussion March 2024
UKCGE Parental Leave Discussion March 2024UKCGE Parental Leave Discussion March 2024
UKCGE Parental Leave Discussion March 2024
 
Diploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdfDiploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdf
 
Prelims of Kant get Marx 2.0: a general politics quiz
Prelims of Kant get Marx 2.0: a general politics quizPrelims of Kant get Marx 2.0: a general politics quiz
Prelims of Kant get Marx 2.0: a general politics quiz
 
General views of Histopathology and step
General views of Histopathology and stepGeneral views of Histopathology and step
General views of Histopathology and step
 
How to Solve Singleton Error in the Odoo 17
How to Solve Singleton Error in the  Odoo 17How to Solve Singleton Error in the  Odoo 17
How to Solve Singleton Error in the Odoo 17
 
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdfMaximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
 
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdfP4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
 
Education and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptxEducation and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptx
 
How to Add a many2many Relational Field in Odoo 17
How to Add a many2many Relational Field in Odoo 17How to Add a many2many Relational Field in Odoo 17
How to Add a many2many Relational Field in Odoo 17
 
How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17
 
How to Show Error_Warning Messages in Odoo 17
How to Show Error_Warning Messages in Odoo 17How to Show Error_Warning Messages in Odoo 17
How to Show Error_Warning Messages in Odoo 17
 
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxPractical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
 
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxPISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
 
How to Add Existing Field in One2Many Tree View in Odoo 17
How to Add Existing Field in One2Many Tree View in Odoo 17How to Add Existing Field in One2Many Tree View in Odoo 17
How to Add Existing Field in One2Many Tree View in Odoo 17
 
How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17
 
M-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptxM-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptx
 

Types of testing

  • 1. Types Of Testing Presented By: Sonam Agarwal 3ird year, IT
  • 2. Introduction & Fundamentals  What is Software Testing?  Why testing is necessary?  Who does the testing?  What do we test?
  • 3. Error ,Bug ,Fault ,Failure  A person makes an Error That creates a fault in software That can cause a failure in operation Bug, Fault & Failure.  Error : An error is a human action that produces the incorrect result.  Bug : The presence of error at the time of execution of the software.  Fault : State of software caused by an error.  Failure : Deviation of the software from its expected result.
  • 4. Objectives of testing  The aim of the testing is to identify all defects existing in a software product. It is not possible to guarantee that the software is error free. This is because of the fact that the input data domain of most software products is very large.  A good test case is one that has a high probability of finding an as-yet-undiscovered error.  A successful test is one that uncovers an as-yet- undiscovered error.  What testing cannot do ? o Cannot show the absence of errors.
  • 5. Objectives of a Software Tester  Find bugs as early as possible and make sure they get fixed.  To understand the application well.  Study the functionality in detail to find where the bugs are likely to occur.  Study the code to ensure that each and every line of code is tested.  Create test cases in such a way that testing is done to uncover the hidden bugs and also ensure that the software is usable and reliable.
  • 6. Verification & Validation  Verification - refers to the set of activities that ensure that software correctly implements a specific function.  Validation- refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements. Verification: "Are we building the product right?" Validation: "Are we building the right product?"
  • 7. Testing Vs Debugging  Debugging is not Testing.  Debugging always occurs as a consequence of testing.  Debugging attempts to find the cause of an error and correct it.
  • 8. When to Start Testing in SDLC Phases of SDLC  Feasibility Study  Requirements Analysis and Specification  Design  Coding  Testing  Maintenance
  • 9. Types Of Testing White Box Testing Black Box Testing System Testing Usability Testing Static Testing Dynamic Testing Performance Test Walkthrough Unit Testing Code Reviews Integration Testing Code Inspection Regression Testing
  • 10. White Box Testing  The internals of software are tested to make sure that they operate according to specification and design.  Test cases are based on internal structure of software.  Areas Code Coverage ,Statement Coverage, Branch Coverage, Condition Coverage ,Loop Coverage, Path Coverage ,Data Flow Coverage. • Techniques o Flow graph testing ,Graph matrices ,Control structure testing , Data flow testing.
  • 11. Static Testing  Static testing of a program carried out without executing the program.  It aims to find defects in the software product in the early stages of software development, so that they can be fixed easily.  It can find errors that occur on paths uncovered by testing  It explores all possible execution paths in a program at compile time.  Who o By a team of individuals. o By individual who didn’t write the code.
  • 12. Code Review o A code review can be done as a special kind of inspection in which the team examines a sample of code and fixes any defects in it. In a code review, a defect is a block of code which does not properly implement its requirements, which does not function as the programmer intended. o Are the variables name meaningful? o Are the variables initialized? o Are pointers initialized properly? o Are there infinite loops? o Has the usage of operators like = and == or & and && been checked or not?
  • 13. Code Inspection  It is the most formal technique.  The aim of this review type is to uncover defects in the document in the early stages of software development and thereby improve the quality of the product.  An inspection is one of the most common review practices found in software projects. In an inspection, a work product is selected for review and a team is gathered for an inspection meeting to review the work product.  The goal of the inspection is to identify defects.
  • 14. Code Inspection(continued…) The stages in the inspections process are: Planning: The inspection is planned by the moderator. Overview meeting: The author describes the background of the work product. Preparation: Each inspector examines the work product to identify possible defects. Inspection meeting: During this meeting the reader reads through the work product, part by part and the inspectors point out the defects for every part. Rework: The author makes changes to the work product according to the action plans from the inspection meeting. Follow-up: The changes by the author are checked to make sure everything is correct. The process is ended by the moderator when it satisfies some predefined exit criteria.
  • 15. Unit Testing  Objectives The primary goal of unit testing is to take the smallest module of testable software, and running it in isolation by using prepared test cases and comparing with the actual result to test the interfaces between modules.  When After modules are coded  Who Developer/programmer  Methods o White Box testing techniques
  • 16. What are Stubs, Drivers ?  A stub is a computer program which is used as a substitute for the body of a software module or a dummy module which simulates the function of a module called by a given module under test.  Driver a module which transmits test cases in the form of input arguments to the given module under test and either prints or interprets the results produced by it.
  • 17. Integration Testing  Objectives To technically verify proper interfacing between modules, and within sub-systems that satisfy functional requirement.  When After modules are unit tested  Who Developers/Programmer  Methods o White Box techniques o Black Box techniques
  • 18. Types Of Integration Testing  Top-Down Integration testing  Bottom-Up Integration testing
  • 19. Top Down Integration Testing A B Stub Stub Stub A B C Stub Stub stub Stub
  • 20. Bottom Up Integration testing Test Drivers Level N Level N-1 Level N-1 Level NLevel N Test Drivers Test Drivers Test Drivers Test Drivers
  • 21. Regression Testing  Objectives o It is used to checks faults, defects propagated to other modules by changes made to existing program. o This testing is used to reduce the side effects of changes. o Testing is done by re-executing the previous versions of the application.  Who Programmers or independent testers
  • 22. Black Box Testing  In the black-box testing approach, test cases are designed using only the functional specification of the software, i.e. without any knowledge of the internal structure of the software.  It explains the process of giving the input to the system and checking the output, without considering how the system generates the output. It is also known as Behavioral Testing.  It attempts to find error in the external behavior of the code.
  • 23. System Testing  Objectives The goal of system testing is not to find out faults but to demonstrate performance.  What The system testing is actually a series of different tests , primary purpose of which is to fully exercise the system. All work to verify that all system elements have been properly integrated and perform allocated functions.  When After Integration Testing  Who Development Team
  • 24. Acceptance Testing  Objectives To verify that the system meets the user requirements. It is the system testing performed by the customer him/herself after the product delivery to determine whether to accept or reject the delivered product.  When After System Testing  Who Users / End Users  Methods o Black Box techniques
  • 25. Alpha Testing  It is a testing in which the version of complete software is tested by the customer under the supervision of developer.  This testing is performed at the developer's site in a control environment under the guidance of a developer.
  • 26. Beta Testing  It is a testing in which software is tested by a customer without the developer being present.  This testing is performing at the customer's site.  Customer records the problems and reports it to the developer then the developer makes appropriate modifications.