↳

Servers were being handled by infrastructure team and as a load test team, we did not have direct access to them but we were free to request data from them if needed. Less

↳

Almost for all questions I answered

↳

1. Practice all the probable scenarios for correlation before you go. like for example, Dynamic Boundaries, Varying length of Dynamic Boundaries, binary boundaries, SaveLen, SaveOffset, Regexp. 2. Know different combination of parameter types, parameter manipulation, and know EVERYTHING about File type parameter, 3. If you haven't done branching in previous projects, just Learn C branching with c conditional statements. 4. if you are reading this, You will already know error Handling. what you know is enough since they didn't ask much about Error Handling. 5. Know Scenario Creation, Different type of Scenarios, and various derivatives of little's law ( finding No. of Users with TPS, Pacing/Think time with only no. of users and TPS, etc) . 6. i never knew Printf(), scanf() could do so many things than just displaying whatever you write. So, yeah, Please read string manipulation, arrays and basic C. 7. know your Web-server, middleware, networks thoroughly, else, you will get struck in the middle with trick questions. one question was, how do you determine the max. concurrent users supported by a web-server. 8. your everyday 2/3 tier architecture which is implemented for your current project. as you need to explain it very briefly 9. Queues, Queues everywhere. why does queue gets created at middleware, how do you know queue is being formed, where is it getting formed, what are memory leaks, how do you identify it, what would you suggest when you find memory leaks, etc. Less

↳

Not able to answer very well as i had only one day prior to interview to prepare. Less

↳

From gathering customer requirements, to preparing load test plan, to execute load test and finally, present report to customers. Less

↳

Record and playback tool (e.g. Vugen) is not capturing anything.

↳

Performance testing