ISTQB Syllabus Summary 12

Comprehending System Testing: Upholding Quality at a Holistic Level

In the realm of software testing, system testing occupies a pivotal role in guaranteeing the comprehensive functionality and performance of an entire system or product. Diverging from component and integration testing, which narrow their focus to specific elements, system testing casts its scrutiny over the end-to-end operations and non-functional attributes of the entire system. This all-encompassing approach to testing plays a pivotal role in risk mitigation, validation of system capabilities, bolstering confidence in system quality, and forestalling defects from infiltrating higher testing tiers or reaching production.

The Aims of System Testing

The principal goals of system testing encompass:

1. Risk Reduction: System testing seeks to unearth and mitigate potential risks that could undermine the system's performance, functionality, or security.
2. Validation of Functional and Non-Functional Behaviors: It ensures that the system's functional and non-functional aspects align with the design and specifications.
3. Confirmation of System Completeness: System testing attests that the entire system is not only complete but fully operational, adept at executing tasks as expected.
4. Cultivation of Confidence in System Quality: By conducting a thorough assessment of the system's end-to-end capabilities, system testing nurtures trust in the overall quality and reliability of the system.
5. Detection of Defects: System testing serves as a detective, identifying defects and issues in the system, enabling their timely rectification.
6. Defect Deterrence: By detecting and addressing defects at the system level, system testing acts as a barrier preventing these issues from infiltrating higher testing tiers or, worse, affecting the production environment.

System testing may also encompass verifying data quality and ensuring compliance with legal or regulatory requisites and standards. Additionally, automated system regression tests can offer assurance that system modifications have not adversely impacted existing features or end-to-end capabilities.

The Testing Environment and Foundation

For effective system testing, the test environment should ideally mirror the final target or production setup. This ensures that the testing outcomes faithfully represent real-world conditions and the actual performance of the system.

The foundation for system testing comprises various work products, including system and software requirement specifications (both functional and non-functional), risk analysis reports, use cases, epics, user stories, and models of system behavior. These work products serve as benchmarks to steer the testing process and validate system behaviors against predetermined criteria.

Common Test Subjects and Anomalies

The typical test subjects for system testing encompass the entire system or product, including applications, hardware/software systems, operating systems, and the system under test (SUT). Furthermore, system configuration and configuration data constitute essential aspects of the testing process.

Instances of common defects and anomalies in system testing involve inaccuracies in calculations, unforeseen system behaviors (functional or non-functional), improper control and data flows within the system, inability to execute end-to-end tasks correctly, and disparities between the system's actual performance and the descriptions found in system and user manuals.

Approaches and Roles

System testing demands a holistic approach that thoroughly examines the overall end-to-end behavior of the system, both in terms of functionality and non-functionality. Testers employ the most suitable techniques based on the specific aspects of the system being tested. For instance, decision tables might be employed to validate whether functional behavior aligns with established business rules.

Typically, independent testers conduct system testing. These testers heavily rely on specifications to accurately assess system behavior. Early engagement of testers in activities such as user story refinement or static testing, such as reviews, proves valuable in reducing misunderstandings and disagreements regarding anticipated system behavior, ultimately leading to more effective defect detection.

In summation, system testing stands as a crucial milestone in the software testing continuum, guaranteeing that the entire system or product aligns with specified requirements and operates as intended. Through the identification and resolution of defects at this level, organizations can confidently release a high-quality system to their users and stakeholders.