Tool recommendation for client server application
Any tool recommendations to load test a desktop client server application? your reply is appreciated
Please describe the application communications architecture between the client and the next upstream server component.
Please describe the development environment/model/API for the communications between client and next server component
Please describe the environment in which your client executes (MAC, Windows, LINUX, UNIX, ...)
Business Logic (Data & web services)
This is the architecture.... Or is it enough to do web services & data base performance testing alone
Sorry, doesn't cut it. Performance testing tools exercise application layer protocols or programming interfaces. The information supplied does not meet the architectural need for that information.
How does your thick client connect to the next upstream tier. You need to know the interface used on the server, the application layer protocol used from client to server and the programming interface used by the developer. You ask is it sufficient to only use web services and database? I haven't got a clue how to answer that because I have no idea if your client uses web services or a direct connection to the database out of the desktop client.
You need information on the operating systems involved. If everything runs on Mac, Mac alone and only Mac then this is going to take you in a completely different direction than something which runs on Windows or LINUX/UNIX.
This is why application architecture and development are core foundation classes of knowledge for performance testers and performance engineers.
Sorry, I thought I had provided enough info. Diving deep into it, it uses web services and data API to communicate. Moreover its in a windows platform.
I have couple of options in tools, either LR or SilkPerformer.... your choice?
Define "Data API" in terms of development interface, application layer protocol, etc....
For the web services piece you can simply record using either SilkPerfmer or LoadRunner in proxy mode to collect the requests. Your "Data API" is likely to require additional handling if the transport being used is not HTTP
J is making a point that you'll need to know what the tech stack is.
Most tool choices will heavily depend on what tech stack you're using. I can't use a SOAP tool to test a WebRTC api. You can't instrument and monitor a unix server using a windows tool.
You'll want to meet with your architect or lead dev and get a good sense of all the layers and protocols used between them. Also want to talk to production support / dev ops to understand the difference between the test/dev environments, and the production environments