ISTQB FOUNDATION 4.0 | Tutorial 15 | Test Levels | System Testing | CTFL Tutorials | TM Square

Summary

This tutorial delves into system testing, a critical phase in the software development life cycle that assesses an application as a whole. It emphasizes the importance of testing the product in a complete form to uncover environment-related defects and non-functional characteristics. The video explains that system testing is not limited to functional testing but also serves as a gateway to non-functional testing, such as portability and usability. It highlights the potential for using simulations, the possibility of different testing teams, and the necessity to address incomplete requirements and product risks within this phase.

Takeaways

• 📚 System testing is a crucial phase in the software development life cycle, focusing on testing the entire application as a single unit.
• 🔍 System testing is necessary to identify issues that cannot be caught at the component or integration levels, such as environment-related factors and system configurations.
• 🚀 System testing serves as a milestone to confirm that the system is functionally ready for further non-functional testing.
• 🔄 Non-functional testing, such as coexistence, portability, and interoperability, often follows system testing to ensure the product's compatibility and performance.
• 👥 System testing can be conducted by an independent test team, separate from those involved in other testing levels, emphasizing the importance of different perspectives.
• 🌐 System testing is not performed in a live production environment but in a simulated environment that closely resembles the target system.
• 🛠 The purpose of system testing includes addressing incomplete requirements that become clearer once the system is fully assembled.
• 🔑 System testing helps in identifying and mitigating product risks that can only be assessed when the complete system is available for examination.
• 🔄 Using simulations of subsystems is a common practice in system testing to ensure comprehensive coverage of the system's behavior.
• 📝 System testing is related to the system specification and may require revisiting and refining requirements based on a holistic view of the product.
• 🔑 System testing is an essential step before moving on to detailed risk analysis and mitigation, which will be covered in more depth in later chapters.

Q & A

What is the primary purpose of system testing?

The primary purpose of system testing is to evaluate the entire application as a single unit, ensuring that it functions correctly as a whole and meets the specified requirements.

Why is system testing considered crucial even after component and integration testing?

System testing is crucial because it checks the application as a whole, considering factors and constraints that cannot be tested at the component or integration levels, such as environmental configurations and system-wide defects.

What are some non-functional testing types that can be conducted after system testing?

Non-functional testing types that can be conducted after system testing include coexistence, portability, interoperability, and installability tests, which assess the system's compatibility and performance in various environments.

Can system testing be performed by the same team that conducted component or integration testing?

No, system testing can be conducted by an independent test team, different from the one that performed component or integration testing, to ensure a higher level of objectivity and thoroughness.

What is the significance of testing non-functional characteristics after system testing?

Testing non-functional characteristics after system testing is significant because it helps to ensure that the system is not only functionally ready but also meets quality standards such as performance, security, and usability.

Why is it not advisable to conduct system testing in a live production environment?

System testing should not be conducted in a live production environment because it is meant to be a controlled, pre-production phase where potential issues can be identified and resolved without affecting end-users.

What does the script suggest about the handling of incomplete requirements during system testing?

The script suggests that system testing can help address incomplete requirements by providing a clearer view of how and where to implement them within the product once the entire system is available for review.

How does system testing help in mitigating product risks?

System testing helps in mitigating product risks by identifying potential issues when the entire system is ready for evaluation, allowing for specialized test cases to be run and risks to be addressed before the product is released.

What is the role of simulations in system testing?

Simulations play a role in system testing by mimicking certain products, services, or subsystems, allowing for testing scenarios that may not be possible with the actual system, thus aiding in comprehensive testing.

What is the relationship between system testing and the subsequent non-functional testing?

System testing serves as an exit criteria for entering into non-functional testing. Once system testing is completed and the system is deemed functionally ready, non-functional tests such as performance, security, and usability tests can be conducted.

How does the script define the environment for system testing?

The script defines the environment for system testing as a controlled, non-live setting that closely resembles the target system. This environment is used to conduct tests without impacting the actual production environment.