Open source tool for testing file download
I have a scenario where I need to test the Performance of the URL, the user comes on to the site and then clicks on the file download link.
when the dialog box opens user needs to click on save. I need to simulate 10 to 50 users and measure the performance of the url.
i have tried J-meter, but the second window dialog box is not recognized, I use a company auto proxy setting and OpenSTA was not working.
Can anyone suggest me with any Open Source tool that does not use proxy but is very helpful in measuring performance.
Re: Open source tool for testing file download
I took a look at your history and your substantial work in functional testing tools at the GUI level may be working against you here. You will need to cultivate your "architectural eye" on client-side architecture to achieve a solution you want.
Most performance testing tools that are able to reproduce multiple users per host take advantage of an API interface for the production of load. And this is the core of your challenge. In the case of an explicit file download or upload the browser kicks of a Windows common file dialog box. The output of this box is trapped by the browser for either submission as part of a get/post request under the covers or where the file output is to be redirected as a part of the file download (where most of the time the download is to memory or cache).
JMETER is capable of downloading the file just file, as is openSTA, and so is Grinder for that matter. Noting that you come from a background rich in QTP, LoadRunner is also very capable in this area (as is Silkperformer, QALoad, ....) What is happening under the covers is that the file download is being trapped by the standard logging mechanism of these tools. So, your file download will show up as a bytestream in the log instead of as a separate and distinct file on your hard drive. There are many reasons why you would not want to have a high amount of disk activity on your load generators associated with file download while your test is running - Having the ability to trap the file download bytestream allows the test developer to control the number of bytes written to the file system.
You can certainly take advantage of validation and correlation mechanisms built into various tools to validate whether a valid formatted file has been sent back in the bytestream. For instance, with PDF files it is common to search for the standard PDF file header and footer in the returned bytestream combined with a size of the recent download as validation mechanisms.
Noting that you are coming from a work background dominated by functional testing it would be in your best interest to work with a very robust performance engineer for your first couple of gigs (this is in addition to tool training). This person can assist you greatly with the process differences between functional and performance testing as well as help to cultivate that aforementioned "architectural eye" to help you move around common items such as the standard file open/save dialog box.
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes