QA/Execution/Web Testing/Load Testing: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
= Tools = | = Tools = | ||
== [http://httpd.apache.org/docs/current/programs/ab.html Apache Bench] == | == [http://httpd.apache.org/docs/current/programs/ab.html Apache Bench] == | ||
* [https://wiki.mozilla.org/User:Clouserw/AMO/loadtest AMO load tests] | |||
== [http://jakarta.apache.org/jmeter/ JMeter] == | == [http://jakarta.apache.org/jmeter/ JMeter] == | ||
* Uses/pros: | * Uses/pros: | ||
Revision as of 19:02, 26 May 2011
Strategy / Approaches / Considerations
Tools
Apache Bench
JMeter
- Uses/pros:
- POSTing repeated and/or random input to a website/application
- Cons:
- Doesn't do JavaScript on its own (or at all? Just via JSON)
- Sample scripts:
- .
- .
Grinder
NetSparker Community Edition
- Uses/pros:
- Fuzz-testing (first and foremost)
- Server stress-testing (up to 200requests/second)
- Cons:
- Community Edition doesn't do authenticated sessions
- Caveat:
- Unless you're stress-testing (in which case, please let IT/NetOps know ahead of time), then set the throttle to 3 or 4