Performance is one key area for improvement. It can be slower compared to other tools I've used. 

Secondly, we have a very limited resource pool that uses this tool in India. So, finding resources familiar with Eggplant in India is challenging due to lack of affiliation programs and so on. 

One area I can think of to improve is the usability of the reports that we get. They could be simplified and easier to read. The language in the reports, on occasion, can be too technical and is not always easy to understand.

On Eggplant's Performance side, it does what we wish and everything we need it to do at this stage. It's integrating very well into the pipeline. Overall, it's helped us. I don't recall any features that are lacking for our use case.

I'd like to see the ability to integrate the user experience through device forms like AWS device forms or source labs.

• Correlation that is automated.
• All-in-one script development and script management interface. Currently, you have to flip between Visual Studio and Eggplant Studio.
• Debugging needs to be improved to include logging of certain items, including response times, line numbers, correlation, and parameter substitutions, etc. When running a test through the controller, you cannot drill down to a specific Vuser log for a specific script with line numbers, parameter/correlation substitutions, etc.
• Script readability - Subrequests are not nested under main request, but relegated to the end of the script for all requests.
• Ability to auto generate script from SOAP, WSDL, REST imports.