CT-PT practice question 7 of 10

Which of the following is a static performance test?

Full set: 40 questions
Answer options
A: Usability test of the user interface
B: Evaluation of the test execution skills of the testers
C: Review of the network architecture Correct answer
D: Formal signature approval by the end users
Correct Answer:
C. Review of the network architecture
Explanation

Static performance testing involves the analysis of system artifacts, such as architecture diagrams or code, without executing the system. Its goal is to identify potential performance defects early in the software development lifecycle. A review of the network architecture is a classic example of a static test, as it examines the design for potential bottlenecks, latency issues, or single points of failure that could impact system performance under load. This proactive analysis helps prevent costly performance problems before the system is even built.

Why Incorrect

A. Usability test of the user interface: This is a dynamic test that requires executing the software to evaluate user experience, not a static analysis of performance.
B. Evaluation of the test execution skills of the testers: This is a personnel or process assessment, not a test of the software system's performance characteristics.
D. Formal signature approval by the end users: This is a project management or user acceptance procedure, not a technical test activity.

References

1. ISTQB® Certified Tester Performance Testing Syllabus (v1.0.1, 2018): Section 2.2.1, "Main Performance Testing Activities," states: "During the design and architecture phases, static testing of the design and architecture can find performance defects early... Examples of static testing for performance include architecture reviews and code walk-throughs." This directly identifies architecture review as a static performance test. (URL: https://www.istqb.org/certifications/performance-testing)

2. Smith, C. U., & Williams, L. G. (2002). Performance Solutions: A Practical Guide to Creating Responsive, Scalable Software. Addison-Wesley Professional. Chapter 3, "Software Performance Engineering," details the methodology of using models and analysis of software architecture and design to predict and evaluate performance attributes before implementation, which is the essence of static performance testing.

3. IEEE Standard for Software and System Test Documentation (IEEE Std 829-2008): While not defining "static performance test" directly, it distinguishes between static analysis (e.g., reviews, inspections) and dynamic testing (execution-based), reinforcing the classification of an architecture review as a static activity. (URL: https://ieeexplore.ieee.org/document/4578383)

Scroll to Top