Software Testing
Prepared by: Ajit Dash
1
Syllabus
Day 1 Day 2 Day 3 Day 4
• Introduction to testing • Testing as a career • Types of applications • QA vs QC
• Why software testing • Qualities of a tester • Verification vs Validation • SDLC
• Importance of software testing • Principles of testing • Advantages & disadvantages of SDLC
Day 5 Day 6 Day 7 Day 8
• Advantages & disadvantages of • STLC • Levels of software testing • Test scenario writing
SDLC (Continue) • Types of software testing • Test plan & Test strategy • Test case writing
• Brief on Agile methodology • Effective way of writing test cases
Day 9 Day 10 Day 11 Day 12
• Error, bug, defect, failure • Testing technology • Defect management tool • Defect reporting
• Bug life cycle • Testing of Web & Mobile • Defect template • Entry exit criteria
• Roles and responsibility in application
every stage • Severity vs Priority
Day 13 Day 14 Day 15
• Requirement Traceability • Doubt clarification • Practice for Interview
Matrix • Hands on testing • Mock interview
• Testing deliverables and
documentations
2
Agenda | Day 1
• Introduction to testing
• Software testing history
• Introduction to software testing
• Importance of software testing
• When to start and stop testing
• Software failure
• Causes of software failure
• Impact of software failure
• How to avoid software failure
• Resource triangle
3
Introduction to Testing
Testing: A procedure for critical evaluation or a means of determining the presence, quality, or
genuineness of something is termed as testing. In general, testing is finding out how well something
works.
What is Software?
Software is a set of instructions to perform some task. Software is used in many applications of the
real world. Some of the examples are, Application software, website, video game, banking app etc.
Introduction to Software Testing?
Software Testing is the process which ensures that the system or application is free from the
inconsistency or unusual behavior and working as per the expected behavior or requirements. It is a
critical element in the software development life cycle and has the potential to save time and
money by identifying problems early and to improve customer satisfaction by delivering a more
defect-free product. Software Testing can be defined in simple words as “Performing Verification
and Validation of the Software Product” for its correctness and accuracy of working.
4
Software Testing History
5
Importance of Software Testing
6
When to Start and Stop Testing?
When to Start Testing?
An early start to testing reduces the cost, time to rework and error free software that is delivered to
the client. In Software Development Life Cycle (SDLC) testing can be started from the Requirements
Gathering phase and lasts till the deployment of the software. It also depends on the development
model that is being used.
When to Stop Testing?
It is difficult to determine when to stop testing, as testing is a never-ending process. It is difficult to
claim that any software is 100% tested. Following scenario should be considered to stop the testing:
• Testing Deadlines or Management decision.
• Completion of test case execution.
• Completion of Functional and code coverage to a certain point.
• Bug rate falls below a certain level and no high priority bugs are identified.
7
Software Failure
Software failure is a term used to label a malfunction, a flaw, a failure or a fault in a computer
program that produces incorrect results. Most software failures arise from errors made by people in
a program's design.
Effect of an Error
An error or mistake leads to a defect which can in turn cause the software failure.
8
Causes of Software Failure
Environmental conditions
– The environment set up for testing the various versions of the code being unavailable on time
Hardware Failures
– Crash of the dependent hardware, loss of versions can impact the code quality
Lack of skilled resources
– Lack of knowledge both Technical and Business can lead to critical, expensive errors
Inadequate reviews / walk-through
– The defects might go unnoticed and cause the failure
Changing Requirements
– Frequent changes to requirements impacts the quality of code and in turn the software
Time constraints to meet up the deadlines
– Rushing up to meet the deadlines leaves many defects being injected into the code.
9
Impact of Software Failure
❑ Loss of money
❑ Loss of time
❑ Loss of business reputation
❑ Injury
❑ Death
Example:
➢ A data breach at T-Mobile affects 50 million customers
➢ ISRO calls off GSLV launch after fuel leak
➢ For over 2 years, Nissan recalled over a million cars for a software glitch in the airbag sensory
detectors.
➢ Amazon saw their products being priced at 1p each
➢ Security Issues in Zoom App
➢ Software Fault was a Cause of Airbus A400M plane crash
➢ Memory Failure - Tesla Recalls 135,000 Vehicles
➢ Tesla has recalled nearly 12,000 vehicles after one of its battery controllers failed and caused the
vehicle to catch fire
10
How to Avoid Software Failure
❑ Have a clear understanding of business requirement
❑ Selecting right team and technology
❑ Deciding the time duration for building the software and cost associated with it
❑ Proper planning
❑ Thorough testing before go live in real time environment
❑ Understanding the risk and accountability
Resource Triangle:
The items at the corner of the triangle are time,
money and quality. These three affect one
another, and also influence the features that are
or are not included in the delivered software. If
we need to deliver a system faster (i.e. in less
time), it will usually cost more.
11
Thank You!
12
