![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
nonethefewerWe're looking for a good load-testing tool at work. We already have/use these things:
* miniprofiler: Used for checking the load times of a page, complete with what specific SQL is running at each given interval of time. (Only in the test environment; it's not on Production, to my knowledge.)
* Firebug: Great for finding minor CSS issues, major JS/XML issues, and load times of background events. For example, when I right-click on an item that pulls up a specific context menu, I want to see how long it takes to load that particular thing; Firebug is useful for showing the post/response information for this.
What I want is something that combines these things, and also exports or auto-exports things to a file for later comparison. It can be web-based, external desktop tool, internal code-based stuff (like miniprofiler), whatever, so long as it does the above things in a reliable comparison-type exporting-type fashion.
The easiest explanation for why: Comparing load-testing of, say, our most-used web page from an earlier release with our current release.
--
Given that we do a lot of jQuery calls, this tool would also need to be able to track user actions (or user-emulating actions; see Selenium). For example, when I right-click and get the context menu, it should track that I manually did this thing, which triggered these actions.
If this could be something that works with our test cases as well, I... well, I might salivate. It would be awkward, but would also be a sign of my undying appreciation.
We use ASP.NET and jQuery, is the extent of my knowledge there. Further code-based questions can be asked (as to what we're using), so long as direction is given as to how I'd find out. (I can read pidgin code, but not necessarily enough to say "we're totally using C#" or whatever.)
It can be something that needs to be paid for, so long as there's a fully functional trial period beforehand. This is for work; I don't need to rely exclusively on FOSS. (Although I do prefer it.)
* loadUI: Entertaining, in that we also sort of use soapUI for API testing.
* Pylot: Pretty good, except it's mostly for automated page loads and averaging, less about getting errors and the like as they happen.
* miniprofiler: Used for checking the load times of a page, complete with what specific SQL is running at each given interval of time. (Only in the test environment; it's not on Production, to my knowledge.)
* Firebug: Great for finding minor CSS issues, major JS/XML issues, and load times of background events. For example, when I right-click on an item that pulls up a specific context menu, I want to see how long it takes to load that particular thing; Firebug is useful for showing the post/response information for this.
What I want is something that combines these things, and also exports or auto-exports things to a file for later comparison. It can be web-based, external desktop tool, internal code-based stuff (like miniprofiler), whatever, so long as it does the above things in a reliable comparison-type exporting-type fashion.
The easiest explanation for why: Comparing load-testing of, say, our most-used web page from an earlier release with our current release.
--
Given that we do a lot of jQuery calls, this tool would also need to be able to track user actions (or user-emulating actions; see Selenium). For example, when I right-click and get the context menu, it should track that I manually did this thing, which triggered these actions.
If this could be something that works with our test cases as well, I... well, I might salivate. It would be awkward, but would also be a sign of my undying appreciation.
We use ASP.NET and jQuery, is the extent of my knowledge there. Further code-based questions can be asked (as to what we're using), so long as direction is given as to how I'd find out. (I can read pidgin code, but not necessarily enough to say "we're totally using C#" or whatever.)
It can be something that needs to be paid for, so long as there's a fully functional trial period beforehand. This is for work; I don't need to rely exclusively on FOSS. (Although I do prefer it.)
* loadUI: Entertaining, in that we also sort of use soapUI for API testing.
* Pylot: Pretty good, except it's mostly for automated page loads and averaging, less about getting errors and the like as they happen.
