QA/Execution/Web Testing/Load Testing: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
(→JMeter) |
||
| Line 5: | Line 5: | ||
* Cons: | * Cons: | ||
** Doesn't do JavaScript on its own (or at all? Just via JSON) | ** Doesn't do JavaScript on its own (or at all? Just via JSON) | ||
* Sample scripts: | |||
** . | |||
** . | |||
== [http://www.mavitunasecurity.com/netsparker/ NetSparker Community Edition] == | == [http://www.mavitunasecurity.com/netsparker/ NetSparker Community Edition] == | ||
* Uses/pros: | * Uses/pros: | ||
Revision as of 18:53, 26 May 2011
Tools
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:
- .
- .
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