Hot answers tagged

46

Looking into JMeter User's Manual will be indeed good as first step (Getting Started, Building a Test Plan, Building a Web Test Plan). Several step-by-step guidelines about JMeter setup and usage for performance/load testing you can find here: - JMeter articles and tutorials: Load Testing your Applications with Apache JMeter Using JMeter Effective load ...


12

There is never a general industry-wide answer to this sort of question. What might be "Key" for your company may very well not be "Key" for my company. To answer this question for your specific context, find out what matters to the stakeholders you serve. Figure out what is important, what is not, and then determine what indicators can help you determine if ...


12

Well I don't think JMeter will help you do performance or load testing of the click action/event of a button. If the click of a button makes an HTTP request to the server, then you can most definitely do performance or load testing for that. How JMeter works is, it takes an HTTP request and throws the specified number of instances (threads/users) on the ...


10

The first thing you need to do is isolate whatever could be messing with your system. Make it as independent as possible. The fewer background processes, extra hardware and software, and even network traffic you can get, the better. Sometimes it's even a good idea to run these on a batch job that runs at night at a time when you know there's nothing else ...


10

I have had some luck using Grinder. It is Java based but you can also write your scripts in Jython or Clojure. You said that you would like to take advantage of your team's current Selenium scripts and expertise performance testing. You did not describe your regression test scripts, but you may want to reconsider whether they are appropriate. In ...


9

JMeter thread can be stopped with standard JMeter sampler Test Action. There are 3 options: Pause, Stop and Stop Now.


9

No. The items you mention scale very differently and there are far too many factors and resources that will get used. For instance if I time requests on a local server using an application I'll find things like 1 user = 10 second response average (time per request) 10 users = 2.5 second average 100 users = 2.5 second average 1000 users = 20 second average ...


9

Does this actually catch, before production, many of the "surprise" problems we might anticipate? Or is there a more fundamental flaw in the approach that will cause deleterious changes to pass testing and affect production? You are wise to have a test system that you can use for catching performance issues, but your "scaling" approach is flawed. ...


8

All right, So Tristann kindly revised his original question to include more details in terms of a scenario. So I'm adding a second answer to more directly address it. Firstly you'd probably want to ask a few more questions about what the customer is most concerned with and what they want tested, here's a small sample: what's the duration of the shoppers ...


8

It's not exactly clear what question you are asking, but let me take a stab. I would deal with it by creating a bug report. In it, I would mention what you are seeing in Commit A, and Commit B. I'd mention that the combination of the two pushes performance past the prescribed limits. From a QA point of view, it's not important at all in which Commit the "...


7

I have put together a really simple article of doing performance testing with Jmeter over here - http://testcy.co.in/performance-testing-jmeter. Even novice users with not much technical knowledge of code can do performance testing using this method. For more tutorials, here you go, http://www.tutorialspoint.com/jmeter/jmeter_tutorial.pdf http://jmeter....


7

Desktop software usually requires installation. Web applications usually do not. But web applications are sometimes expected to be running 24x7. This can make upgrades and maintenance more of a challenge to plan and execute (and thus test) In addition to browser versions mentioned by others here, you may need to worry about browser add-ons You may also need ...


5

There are a lot of performance testing tools: Apache Bench The Grinder Siege Pylot Setup for the most part is very easy. You could run each of these packages on a local VM; however, if you want to simluate large loads of traffic you need to have a machine with a little more RAM and Processor. Since this is an AJAX application you might have to simulate ...


5

I do not think the UI testing is very different: field validation, default values, resizing, scalability, and so on. You probably need to support more than one brand and version of web browser, and perhaps even some mobile devices. You may want to separate your business logic tests from your browser-level tests so that you do not repeat every test on ...


5

you could use a plugin, although there is a simpler way. You can create a CSV file with the list of usernames and passwords you want to iterate through and then create a datasource. When you execute the web test, it will iterate through all of the items in the CSV file, one line for each test execution. Based on what you outlined above I would probably ...


5

Please see the following link: http://jmeter.apache.org/usermanual/test_plan.html#thread_group The 'number of threads' are equivalent to the number of concurrent users that you are looking for. In your scenario above, you have 20 concurrent threads (users) and each thread will run 10 times.


5

JMeter is a good choice. Kindly find answers on your queries below: Also, I'm not sure if I can define requests dynamically, based on the results of previous request. You can. Particularly for REST web services I would recommend installing Extras with Libs Set of JMeter Plugins project which provides JSON Path Extractor so you will be able to work with ...


5

First ask your client that 'How many users their website intend to support?' From client you should get the number of users during Peak Load (Y) and Normal Load (X) and their expected Response Time, some clients say make it as fast as possible, but never go for this wording, ask him about the numbers. Then start running your script from 1 to X to Y in an ...


5

Presumably the database is just a piece of your overall system, and your goal is to determine whether database changes break things or slow the system down. Using a downsized database is a reasonable way to check whether database changes break things. I'm not sure it makes sense to use a downsized database for load testing. Whether this makes sense ...


4

You should not focus on the concurrency rate, rather try to get traffic statistics, such as visits, amount of activity, and so on. If you already have a site running, you can analyze the server logs or any audit trails your application might write. When your site is still offline and you just want to go live, you have to come up with some expectations for ...


4

I wrote about concurrent users and numbers in a blog post: http://blog.xceptance.de/2011/06/07/get-the-right-load-mix-out-of-a-few-numbers/ Wait… where are my concurrent users? This is simple: “concurrent users” is an inaccurate way of describing traffic, so we have not used that number yet. Why is that? To get to the bottom of that, we ...


4

Combinatorial explosion of varieties: You may need to test each version of each browser on various hardware running various operating systems Front-end testing can be easier because of the universality of the displayed information When you do performance/load testing you're simultaneously testing the machine the server is on, not the current desktop (unless ...


4

Apart from "what those other guys said", all of it very good advice, some other considerations I'd recommend are: Usability - Desktop applications tend to have a help file built in, where web applications should be more or less self-explanatory. Load times - this one is a big pain point. Not everyone has broadband (and we won't go into how much I despise ...


4

It depends on the goal of your testing, the system and how complex it is, how easy it is to monitor, how much information is logged and I'm sure some other factors that I am missing. I can give you specific examples of where I have used MFAT in "performance" testing and it made a lot of sense. I put performance in quotes because it is generally used as a ...


4

user1108631, welcome to SQA. Depending on how the terms are used and who you are talking to, performance tests can be a different beast from stress tests. For brevity, I will only refer to performance tests, but I think my answer is applicable to both. It is hard to answer your first question without knowing more about the server. If a performance test ...


4

Lyndon is half right. To clarify - Visual Studio web performance tests (coded or otherwise) will not ever execute JavaScript - either in a browser or by any other means. The article Anicho references states "You can use coded a Web performance test to simulate the logic typically performed by JavaScript" You can craft them however to execute xmlhttp ...


4

The answer to this question is obvious: it depends. As an example, the customer complained on that the report generation pages takes a lot of time ~ 4 minutes to generate the report. Our developers were not able to fix the performance without rewriting the legacy code from scratch. So they just added “ajax-like” loading indicator. Well… our customers were ...


4

There are no tools that can provide you client-side rendering times. Client side rendering is not a measurable value, unless all of the devices accessing the system are identical in terms of hardware and network access to the SUT. However, It is completely viable to do a stopwatch test of the total page rendering time, as long as you communicate to the ...


4

The deliverable is information about the system. The purpose is to help people make better decisions, based on information about the system.


4

It depends on what your test is doing. If it's something long enough - it will be 20, if it's something very short - it'll be 1. JMeter offers several options to control the load. In particular the most commonly used elemends are: Synchronizing Timer - to pause threads unless certain number will be reached and fire them all at the same time. Constant ...



Only top voted, non community-wiki answers of a minimum length are eligible