QA/Execution/Web Testing/Load Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
= Tools =
= Tools =
== [http://jakarta.apache.org/jmeter/ JMeter] ==
== [http://jakarta.apache.org/jmeter/ 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)
== [http://www.mavitunasecurity.com/netsparker/ NetSparker Community Edition] ==
== [http://www.mavitunasecurity.com/netsparker/ NetSparker Community Edition] ==
* Use(s):
* Uses/pros:
**Fuzz-testing (first and foremost)
**Fuzz-testing (first and foremost)
**Server stress-testing (up to 200requests/second)
**Server stress-testing (up to 200requests/second)
* Cons:
** Community Edition doesn't do authenticated sessions
* '''Caveat''':
* '''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'''
**'''Unless you're stress-testing (in which case, please let IT/NetOps know ahead of time), then set the throttle to 3 or 4'''

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)

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