Software Testing

Introduction
• Software testing is the process of verifying that software meets specified
requirements and works as intended.
• The primary objective of software testing is to identify defects or errors
that might have been introduced during the development process.
• This can help in improving the quality and reliability of the software and
minimizing the risk of failure.
 Types of Software Testing

• Functional Testing: Verifies that the software meets functional

requirements, including black-box and white-box testing.
• Non-Functional Testing: Verifies that the software meets non-functional
requirements, including performance, usability, and security testing.
• Structural Testing: Verifies that the software is structured correctly,
including code coverage testing, mutation testing, and static analysis.
 Black-Box Testing

• Black-box testing is a type of functional testing that verifies the

functionality of the software without knowledge of its internal workings.
• It focuses on the external behavior of the software and tests it against
predefined inputs and expected outputs.
• Example: A black-box test case for a calculator application would involve
providing inputs such as 2+2 and verifying that the output is 4.
 White-Box Testing

• White-box testing is a type of functional testing that tests the functionality

of the software with knowledge of its internal workings.
• It focuses on the internal logic and structure of the software and tests it
against the source code.
• Example: A white-box test case for a calculator application would involve
testing the code that performs the addition operation
 Performance Testing

• Performance testing is a type of non-functional testing that tests the speed,

scalability, and stability of the software under different load conditions.
• It helps in identifying performance bottlenecks and improving the overall
performance of the software.
• Example: A performance test for a website would involve simulating
thousands of concurrent users and measuring the response time.
 Usability Testing

• Usability testing is a type of non-functional testing that tests the ease of

use, user interface, and user experience of the software.
• It helps in identifying usability issues and improving the overall user
experience of the software.
• Example: A usability test for a mobile app would involve observing users
as they perform tasks such as navigating the app or making a purchase.
 Security Testing

• Security testing is a type of non-functional testing that tests the security of

the software to identify vulnerabilities and potential threats.
• It helps in identifying security risks and improving the overall security of
the software.
• Example: A security test for a web application would involve attempting
to hack into the system or injecting malicious code.
 Code Coverage Testing

• Code coverage testing is a type of structural testing that tests the code
coverage of the software to identify areas of code that have not been
executed during testing.
• It helps in improving the overall code quality and reducing the risk of
defects.
• Example: A code coverage test for a software application would involve
measuring the percentage of code that has been executed during testing.
 Mutation Testing
• Mutation testing is a type of structural testing that tests the ability of the
software to detect and respond to changes in input.
• It helps in improving the overall fault tolerance and reliability of the
software.
• Example: A mutation test for a flight reservation system would involve
injecting faults or errors into the input data to verify that the system can
handle them.
 Case Study 1: Therac-25 Radiation Therapy
Machine

• In the 1980s, the Therac-25 radiation therapy machine was involved in several accidents
that caused serious injuries and deaths.
• The cause of the accidents was traced to a software error that caused the machine to
deliver excessive radiation doses to patients.
• The software had not been adequately tested and validated, and the system did not have
proper safety mechanisms in place.
• The case study highlights the importance of rigorous software testing and the need for
safety-critical systems to have robust testing and validation processes in place.
 Case Study 2: Ariane 5 Rocket

• In 1996, the Ariane 5 rocket exploded shortly after liftoff, resulting in the loss of the
rocket and its cargo.
• The cause of the failure was traced to a software error in the rocket's guidance system,
which was not designed to handle the high velocity of the rocket.
• The error was caused by the reuse of software from the Ariane 4 rocket, which had a
different flight profile and did not experience the same velocity.
• The case study highlights the importance of designing software systems that are
appropriate for their intended use and the need for careful consideration of software
reuse.
 Best Practices for Software Testing

• Define clear and measurable testing objectives and goals.

• Develop a comprehensive test plan that covers all aspects of the software.
• Use a combination of different testing techniques and methodologies.
• Use automated testing tools where possible to increase efficiency and consistency.
• Involve stakeholders and users in the testing process to ensure that requirements
are met.
• Continuously monitor and evaluate the effectiveness of the testing process.
 Challenges in Software Testing

• The complexity of modern software systems.

• Time and resource constraints.
• Lack of standardization and consistency in testing methodologies.
• Difficulty in replicating real-world environments and scenarios.
• Dependence on human judgment and expertise.
• Balancing the trade-off between testing thoroughness and testing
efficiency.