Any testing process is meaningless without a goal, metrics can often act as the goal when it comes to performance testing. When it comes to performance testing goals the focus should be on metrics like throughput, response time, Latency, Error percentage, etc.
By performing the performance testing, based on these metrics, we can assure the performance of a web application or an API, or any system.
if a tester is not able to identify the right metrics in the early stage itself, it will be hard to reach any consultation and to put an end to the testing process.
Definitely, the environment setup process, less information about the expected requirement and the hardest one, not having a clear picture regarding the goal of the performance testing.
In performance testing, the focus will be on finding the bottleneck of an application, but in performance engineering, the focus is to reduce those bottlenecks and to improve the performance of the application. So, as a QA engineer, finding the bottleneck or any performance-related issue is not enough nowadays, we must learn or think about how should we overcome those issues.
Moreover we, the QA engineers are responsible for the quality of the application that will reach the end-user.
In the real-time scenario, we’ll not be able to assume the user traffic of an application, it may increase, decrease or remain constant over a certain period of time
To generate that kind of real-time scenario we must perform spike or stress testing to ensure that the application has what it takes to deal with the sudden change in the traffic volume.