In Trusted Tester, how should perf and stability testing be approached?

• A. Measure response times, frame rates, CPU/memory usage under realistic load; identify performance regressions.
• B. Test only under light usage.
• C. Rely exclusively on user feedback.
• D. Focus only on startup time.

Answer: (A)

Performance and stability testing hinges on evaluating how the product behaves under realistic use, using objective measurements and baselines to spot regressions. To do this well, you measure key metrics like response times, frame rates, and CPU/memory usage while the system handles typical user loads, including peak conditions. This approach shows how the product performs in real scenarios and whether recent changes have slowed things down or caused resource issues. Stability comes from long-running or stressed tests that reveal memory leaks, crashes, or degraded responsiveness over time, ensuring the system remains reliable under sustained use. By comparing current results to established baselines from previous versions, you can identify regressions—areas where performance or stability worsened.

Other approaches fall short because testing only under light usage misses problems that appear under normal or heavy load, relying solely on user feedback lacks objective data to detect subtle regressions, and focusing only on startup time ignores ongoing performance and the overall stability during regular operation.