ISTQB CT-PT Dumps

One of thebest practices in performance test scriptingis tovalidate that correct data is recorded in the databaseafter execution. This ensures thatperformance issues do not impact data integrity.

Option A (Increasing the number of scripts)may providemore coverage but does not verify accuracy.

Option C (Adding transaction timers)is useful for performance monitoring but does not ensurecorrect data entry.

Option D (Holding the development team accountable)is amanagement responsibility, not a scripting best practice.

Performance testing istime-sensitiveand must be designed tofit within the constraintsof the project timeline. If performance tests take too long to execute, they may not be feasible within a given sprint or development cycle. The results should be reproducible, meaning the same test on an unchanged system should yield the same results (making option C incorrect). While stakeholder expectations are important, performance tests should be objective and based on defined benchmarks rather than subjective expectations (making option D incorrect).

Spike testingis a type of performance testing that evaluates how a systemresponds to sudden, extreme increases or decreases in load. It is designed to simulateunexpected surges in user activity or workload, such as flash sales, viral events, or cyberattacks.

Option A (Gradual load increase testing)describesload testing, not spike testing.

Option B (Handling expected peak load)describesstress testing, which pushes the system to or beyond its limits but does not focus on sudden changes.

Option C (Meeting future efficiency requirements)relates tocapacity planningrather than spike testing.

Spike testing helps toidentify system bottlenecks, resource allocation issues, and performance degradationwhen traffic surges unexpectedly.