System Testing with examples | Software Engineering

Summary

In this video, the concept of system testing is explained using real-life examples, particularly focusing on the testing phases of a software product. The presenter walks through different testing types, including unit, integration, and system testing, using the analogy of testing a car. System testing ensures that the fully integrated software works according to user specifications, using black box testing to verify outputs without delving into internal workings. The video also discusses testing categories like alpha, beta, and acceptance testing, along with functional and non-functional testing, such as load and stress testing.

Takeaways

• 😀 System testing is the final phase of testing where the entire integrated system is validated to ensure it meets all specifications.
• 😀 Black box testing focuses on the system's functionality, ignoring its internal structure, and checks if the expected outputs are achieved from given inputs.
• 😀 White box testing involves looking at the system's internal structure, often used in earlier testing phases like unit and integration testing.
• 😀 System testing is compared to testing a fully assembled car, where only the functionality (driving, braking) is tested, not the internal workings.
• 😀 Alpha testing is done by the development team to ensure the system works as expected before external testing.
• 😀 Beta testing involves trusted individuals outside the development team, similar to showing a movie to a small audience before public release.
• 😀 Acceptance testing is performed by the client or end user to decide whether the system meets their expectations and is acceptable for release.
• 😀 Functional testing checks if the system performs its intended functions, such as a car's brakes or engine working properly.
• 😀 Non-functional testing includes performance checks under stress, load, and scalability to ensure the system works under different conditions.
• 😀 Load testing checks if the system performs under standard conditions, like ensuring a car can carry its specified number of passengers.
• 😀 Stress testing pushes the system beyond its limits, such as testing a car with more passengers than it’s rated for, to see how it performs under pressure.

Q & A

What is System Testing?

System Testing is the final phase of software testing where the complete and fully integrated software system is tested to ensure it meets all the specifications outlined in the Software Requirements Specification (SRS). It validates the system as a whole after all individual components have been integrated.

How does System Testing differ from Unit Testing and Integration Testing?

Unit Testing focuses on testing individual components of the system, and Integration Testing checks if those components work together when combined. System Testing, on the other hand, tests the entire system as a whole to ensure it meets all the specified requirements.

What does Black Box Testing mean in System Testing?

Black Box Testing refers to testing the system based on its inputs and outputs, without considering its internal structure or workings. In System Testing, this approach means testing the functionality of the system without worrying about how it operates internally.

Can you provide an example of Black Box Testing?

An example of Black Box Testing is testing a car. Once the car is fully built, you start the car and drive it, without worrying about how the internal parts like the engine or fuel system work. You just check if it works as expected when given specific inputs, such as starting the car and driving.

What is the difference between White Box and Black Box Testing?

White Box Testing focuses on the internal workings of the system, such as the code, logic, and structure. Black Box Testing, on the other hand, focuses on testing the system's functionality and output without examining the internal workings.

What are Alpha, Beta, and Acceptance Testing?

Alpha Testing is done by the development team to ensure the system is working as intended. Beta Testing involves testing by a select group of users outside the development team. Acceptance Testing is when the client or end user tests the system to decide if they will accept it based on its functionality.

What is the purpose of Functional Testing in System Testing?

Functional Testing is aimed at verifying if the system's core functions are working as expected. For example, testing if the car’s braking system, locking system, and other key functionalities are working properly.

What is Non-Functional Testing, and how does it differ from Functional Testing?

Non-Functional Testing focuses on aspects of the system that are not related to specific functions, such as performance, scalability, load handling, and stress testing. Functional Testing, on the other hand, ensures that specific system features work correctly.

What is Load Testing and how is it related to System Testing?

Load Testing is a type of Non-Functional Testing where the system is tested with a normal load to ensure it performs well under expected usage. For example, testing if a car can carry the number of passengers it is designed to accommodate.

What is Stress Testing, and why is it important in System Testing?

Stress Testing involves testing the system under extreme conditions, such as applying more load or pressure than the system is designed to handle. This helps evaluate how the system performs under stress and identifies any potential weaknesses.