Which of the following is a general principle of performance testing?

A fundamental principle of any testing activity, including performance testing, is that it must be practical and provide value within the project's constraints. Performance tests must be designed, executed, and analyzed within the available project timeframe to provide timely feedback for decision-making. If tests take too long to run, the results may become irrelevant as the system under test will have already evolved, making the feedback obsolete. This aligns with the core project management aspect of testing.

B. Test results must be comparable to tester expectations. This is imprecise. Results are compared against pre-defined, objective performance requirements and criteria, not a tester's subjective expectations.
C. Test results must vary when the tests are run repeatedly on an unchanged system. This is incorrect. A key principle is repeatability; results should be consistent and reproducible on an unchanged system to be considered reliable.
D. Tests must align with the ideal outcome of stakeholders. This is too vague. Testing aligns with specific, measurable, and agreed-upon performance requirements derived from stakeholder needs, not their potentially unrealistic "ideal" outcomes.

1. ISTQB® Certified Tester Performance Testing Syllabus (2018): Section 2.4, "Managing a Performance Test Project," emphasizes the role of the performance test manager in "creating a realistic schedule for performance testing activities" and "tracking the progress of the performance testing activities against the schedule." This directly implies that tests must be executable within the project timeframe to be manageable and effective.

2. The Art of Software Testing, 3rd Edition (G. J. Myers, C. Sandler, T. Badgett): While a general testing book, it establishes the universal principle that testing operates under constraints. Chapter 2 discusses the economics of testing, noting that "you can't test everything" and that testing efforts must be planned and budgeted, which inherently includes time constraints. This principle applies directly to specialized testing like performance testing.

3. A Practical Guide to Testing in DevOps (K. E. Block): In the context of modern development, this guide emphasizes the need for fast feedback loops. Chapter 5, "Performance Testing," discusses integrating performance tests into the CI/CD pipeline, which requires tests to be "fast enough to provide timely feedback." This reinforces the principle that test execution time is a critical constraint.