testing in web vs client/server
I've been testing an app (content management system with .exe and web clients) that supports up to 2k users and my main duty is performance and stability testing. During my interviews though and in the job descriptions I generally hear they want QA Engineers with experience testing "high-transaction" websites.
When I explain we'd execute particular operations thousands of times, observe uptime of server and DB during these tests I get the impression from these people that testing an application deployed on the web requires a much different skill set which confuses me based on what I read.
How does the concept of performance/load/volume testing change so much in a web environment vs traditional client/server?
Re: testing in web vs client/server
Depends on your business requirement and personally I dont see any difference between client server and web application with regard to testing,but yes client server application testing is sometimes more tedious given that we have some restriction with respect to client like client cannot have more than one instances etc.