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
Effective load ...
A service-level agreement is an agreement between two or more parties, where one is the customer and the others are service providers. This can be a legally binding formal or an informal "contract" (for example, internal department relationships).
The agreement may involve separate organizations, or different teams within one ...
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 ...
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 ...
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 ...
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 ...
As you have mentioned that when you access the application without a proxy it works fine, but when using via proxy (recording script for JMeter) you are not able to access the application.
From this I understand you are using JMeter's built-in script recorder. Well it does create some problems some times, because some applications don't work well on proxy.
Answering the comments above,
Well I had Java and Jmeter installed correctly with ClassPath and everything. I also tried running Command Prompt as Administrator but got the same result. There was no problem in that. That is why the GUI version was working properly in first place.
After a lot of R&D and Googling I found out that the problem was with the ...
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 = 2 second response average (time per request)
10 users = 2.5 second average
100 users = 2.5 second average
1000 users = 20 second average
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
You are wise to have a test system that you can use for catching performance issues, but your "scaling" approach is flawed.
If you already have a .jtl result file you can do it like:
jmeter -g /path/to/jtl/file -o /where/you/want/to/store/dashboard
If you would like the dashboard to be generated after the test run, you can run JMeter in command-line non-GUI mode like:
jmeter -n -t /path/to/testplan -l /path/to/result.jtl -e -o /path/to/dashboard/folder
See Full list of ...
I learn Gatling using the resources I found online and experimentation. Just google "Gatling tutorial", there are plenty of links to pages showing Gatling basics, many focus on different aspects so it's useful to read a number of them. I
always found official resource helpful, The Gatling documentation 3.0 is pretty good as well, they also have an Advanced ...
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
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,
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 "...
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 ...
This is not QA decision but business decision. If performance is satisfactory for the customer - it is good enough.
Also remember that the most important speed is speed to the market - deliver most value for your customers to make money to support additional development of the product. If product is late to the market, and is beaten by inferior competition, ...
The terms “performance requirement” or “performance attribute” are preferred over “non functional requirement” according to the most recent update of The IEEE Standard for Software Quality Assurance Processes 730-2014 Definitions.
The IEEE Standard for Software Quality Assurance Processes 730-2014 defines Performance requirement as the measurable criterion ...
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 ...
Please see the following link:
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.
I would recommend JMeter as:
JMeter: free and open source
MSVS: Test Professional costs around $2000 per developer.
MSVS: Windows only
JMeter: HTTP, FTP, JDBC, SOAP, TCP, JMS, SMTP, POP3, IMSP
However if your company has Microsoft products based development infrastructure, like Team ...
The easiest way to resolve this issue is to place the CSV file on all servers (Master and Slaves) inside the Bin directory of JMeter and don't specify any path for the CSV file inside the your JMeter test plan i.e. don't use C:\Data\Files\abc.csv in your test plan, use only abc.csv (and place this file in Bin directory). Also, it will be good to keep the ...
A web search of the terms resulted in,
Scalability Testing, is the testing of a software application to measure its capability to scale up or scale out in terms of any of its non-functional capability.
Performance, scalability and reliability testing are usually grouped together by software quality analysts.
The main goals of scalability testing are to ...
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
There are a lot of performance testing tools:
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 ...
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 ...
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 ...
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.
'Also JMeter concurrent threads are not "concurrent users" as real-life people do pauses between actions on web pages. If you don't set any pauses in your tests then 20 concurrent threads will stand for something like 200-250 concurrent users.'
Yes, I am in an argument with a client about this fact. They are thinking 50 Threads = 50 Users. But there are no ...