QA/Execution/Web Testing/Tools: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
* Load-testing Tools: | * Load-testing Tools: | ||
** https://wiki.mozilla.org/QA/Execution/Web_Testing/Load_Testing | ** https://wiki.mozilla.org/QA/Execution/Web_Testing/Load_Testing | ||
= Strategy / Approaches / Considerations = | |||
= Tools = | |||
== [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] == | |||
* 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: | |||
** . | |||
** . | |||
== [http://grinder.sourceforge.net/ Grinder] == | |||
== [http://www.mavitunasecurity.com/netsparker/ 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''' | |||
== [http://www.joedog.org/index/siege-home Siege] == | |||
= References = | |||
* [http://www.opensourcetesting.org/performance.php Open Source Testing's great page on tools] | |||
== Useful Tools == | == Useful Tools == |
Revision as of 15:40, 26 June 2015
Here is a list of suggested tools & resources
Performance and Load-Testing Tools
- Performance-testing Tools:
- Load-testing Tools:
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
Siege
References
Useful Tools
- HTML5 validator:
- Link-checkers:
- W3C's Link Checker
- Xenu Windows link-checking app
- Tool lists
Security
- Web QA Security Checklist
- Burp Suite; proxy for testing security
- OWASP
- WebGoat security-learning tool
- Scanners/Fuzzers:
- XSS Me
- SQL Inject Me
- Netsparker Community Edition
- PowerFuzzer Windows fuzzing tool
- Acunetix Community Edition scanner
Infrastructure / Server Info
Internal access only
Tips and Pointers
- Tips and pointers to testing the various projects:
Reference Links
- B2G Tips & Tricks
- Webdev
- Web Production Team
- Website Localization
- IT Acceptance
- IT's Service-Level Agreements
- Launch Checklist
- User Agent Strings
- Awesome Unicode stuff
- Continuous Deployment
- Etsy.com video: http://www.livestream.com/etsy/video?clipId=pla_adbab6e2-c629-4bfe-b1fd-21c898693282
- Flickr video: http://vimeo.com/24542044
- James Socol's blog post: http://coffeeonthekeyboard.com/the-future-of-sumo-development-511/