- What criteria would you use to select Web transactions for load testing?
- For what purpose are virtual users created?
Please visit Alex Samourin’s collection of load testing questions.
Please visit Alex Samourin’s collection of load testing questions.
10 Comments on Load testing SQA interview questions
how to test web application(manual and automation) and what is the differerence between
web testing and client/serverapplication.
how to test load,stress and performance test for web.
how to test web application(manual and automation) & how to test load,stress and performance test for web. can you please send me steps.
what is the procedure to test (manual)the web application.
Testing (Load) the Web Application in manual is a tedious task and can’t hence we require to opt the automation testing using some Load testing tool based on the application which is compatible for the Tool which you use. Basically we require to plan the scenarios based on the web application we are testing againt it is based on what the applciation is actually comprised of.
Difference between Web based Application and client server Application :
Web-based apps are a form of client Server, but not all client server apps are web based.
Web based uses standard internet protocols, HTML, and so on. Client server apps can use those protocols, but they don’t necessarily have to.
Plus, client server usually implies a bit more activity at the client, where you have more of an application there, one which gets the data it works with from a server but does a fair amount of work at the client.
A web app leans more toward the client merely viewing the presentation that has been created at the server
Load Stress and Peroformance testing defination Please refer some site
Thanks
Illur Iqbal
Bangalore, India
May be weird, but i wonder if we have to writeup the test cases for Load/ Stress Testing?
Does it make difference in case of Distributed model? or Client Server application?
Hi,
I need some of the answers for the questions in testing ?
how do we calculate test cases ?
how will we know that all test cases are completed ( based on srs) ?
without design specification , how will we write testcases ?
When we convert the Client/Server application to web Application can we use same Automation Scripts?
Give the test case id for the test case which you covered the funcationality and count the number of test cases.
Give the Test Case id for each Testcase and Map the testcase for each requirement. That means requirements that is SRS have some fearure numbers or feature request numbers. So map those numbers with test case ids.
Remember in one Test Case there will be multiple steps for coverint the entire scenario.
You can use “USECASES” for writing test cases. And remember onething, for writing test cases we need requirements.
please correct me if i am wrong
First of all
When developing a software we need SDLC
SDLC contains Different phases
Requirements –> Design –> Coding –> Testing –> Maintanence.
For Software Develpment we need Project Plan
For Testing we need Test Plan at the same time there is STLC — Software Testing Life Cycle.
For any testing, Web App, Clinet-Server, Embedded, Performance Testing
We need a test plan and Testng Process
Testing varies depends on organization. Each organization has its own process and at the same time in organization itself there will be multiple projects and the projects will follow the process depends on the client requirments and client availbility.
For web application the functionaliyt, security,availiblity, performance are very important. For web simply you need a browser and an url
For Client\Server the concentration should be on Configuration testing and Compatibility testing.
C/S can work on all OS’s. We need to test on all OS’s and with defferent configurations.
Correct me if i am wrong.
Warning: session_destroy() [function.session-destroy]: Session object destruction failed in E:\projects\ApacheSites\gispm\logout.php on line 3
Warning: Cannot modify header information - headers already sent by (output started at E:\projects\ApacheSites\gispm\logout.php:3) in E:\projects\ApacheSites\gispm\logout.php on line 4