Debugging load test issues
Functional testing, as described previously, is like taking a scalpel to your application and carefully probing individual functions. Ideally, each tester has a dedicated system, or at least of the core elements, so that you can completely control what happens there. When there is an issue, the logs are silent except for the single operation you performed, aside from any regular background processing. It’s easy to isolate useful information.
When load testing, that’s not the case. Having created a million users, finding the one that failed can be challenging. Performing even a single operation can have a cascade of effects across your system. Creating a single user might involve loading an interface, accepting input, sending that to the backend, and writing it to storage. There may be many other impacts, depending on your system’s architecture.
To debug issues successfully during load testing, you must be thoroughly proficient at...
