Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
76 views15 pages

Software Testing Guide & Methodologies

Uploaded by

rupkumar8084
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
76 views15 pages

Software Testing Guide & Methodologies

Uploaded by

rupkumar8084
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Software Testing

Submitted To:
1. Pavani (230101120241)
2. Achhutha Reddy (230101120245)
3. Pawan Kalyan (230101120243) Guided by :-
4. Rup Kumar (230101120246)
Manoj padhi
CONTENT
 Introduction
 What is Software Testing ?
 Objectives of Testing
 Goals of Testing
 Testing Methodologies
 Software Testing lifecycle – Phases
 Conclusion
INTRODUCTION
 Testing is a process used to help identify the
correctness, completeness and quality of
developed computer software. With that in
mind, testing can never completely establish
the correctness of computer software.
 There are many approaches to software testing
from using alm tools to automated testing, but
effective testing of complex products is
essentially a process of investigation, not
merely a matter of creating and following rote
procedure.
WHAT IS SOFTWARE
TESTING?
Executing software in a simulated or
real environment, using inputs selected
somehow.
OBJECTIVES OF TESTING
Uncover as many as errors (or bugs) as possible in a
given product.

Demonstrate a given software product matching its


requirement specifications.

Validate the quality of a software testing using the


minimum cost and efforts.

Generate high quality test cases, perform effective tests,


and issue correct and helpful problem reports.
ERROR, BUG, FAULT &
FAILURE

Error : It is a human action that produces the


incorrect result that produces a fault.
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. It is an event.
GOALS OF TESTING
 Detect faults
 Establish confidence in software
 Evaluate properties of software
 Reliability
 Performance
 Memory Usage
 Security
 Usability
TESTING
METHODOLOGIES
 White box testing
 Black-box testing
 White box testing
 Knowledge of the internal program design and
code required.
 Tests are based on coverage of code
statements, branches, paths, conditions.

 Black box testing


 No knowledge of internal program design or code
required.
 Tests are based on requirements and functionality.
WHITE-BOX TESTING

Test data

Tests Derives

Component Test
code outputs
BLACK-BOX TESTING
SOFTWARE TESTING LIFECYCLE -
PHASES

• Requirements study

• Test Case Design and Development

• Test Execution

• Test Closure

• Test Process Analysis


REQUIREMENTS STUDY

 Testing Cycle starts with the study of client’s


requirements.

 Understanding of the requirements is very


essential for testing the product.
CONCLUSION
 In order to be cost effective, the testing must be
concentrated on areas where it will be most
effective.
 The testing should be planned such that when
testing is stopped for whatever reason, the most
effective testing in the time allotted has already
been done.
 The absence of an organizational testing policy
may result in too much effort and money will be
spent on testing, attempting to achieve a level of
quality that is impossible or unnecessary.
Thanks

You might also like