Created
June 24, 2013 10:37
-
-
Save nghinv/5849198 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Table of Contents | |
I. RESPONSIBILITIES 1 | |
II. NEEDED SKILLS FOR PERFORMANCE TESTING 1 | |
III. NEEDED SKILLS FOR SECURITY TESTING 2 | |
======================= | |
I. RESPONSIBILITIES | |
1. Performance benchmark: | |
1. Make official performance benchmarks with reporting during Release Test Campaigns | |
2. Make weekly performance benchmarks with comparative reporting to raise alerts when performance regression occurs. Make a wiki + mail weekly reporting on comparative performance benchmarks | |
3. Make on-demand performance benchmarking to help Project Teams to validate, on a performance point of view, a new development, an improvement or a refactoring. | |
4. Make on demand profiling with JProfiler | |
2. Code Quality: | |
1. Code Quality: Measure the Development Standards rules respect and make reporting (mainly with Sonar) | |
3. Security: | |
1. Make a study to find tooling on Software Security analyze (mainly for the UI Part) | |
2. Make Security Analyze of our Products (XSS, …) | |
4. DataSet: | |
1. Create, maintain and document data sets for projects / product testing (focused on performance testing) | |
5. QA Factory and Tooling: | |
1. Study (or Create if no other choice), maintain and document the necessary tooling for performance benchmarking and security subjects | |
2. Automation: all the recurring activities of the Technical QA should be automated as much as possible | |
3. Build, operate and maintain the QA Factory VN. Keep the QAF VN consistent with the QA Factories of others countries and the Software Factory (SWF) | |
II. NEEDED SKILLS FOR PERFORMANCE TESTING | |
1. Require to smart, curious and work hard, to be passionate in performance testing | |
2. Programming skills | |
Application: application for linux/Windows, web applications is preferred | |
Language: java/C# is preferred, good in using regular expression, know well XML format | |
Web application knowledge: HTML, javascript, browsers features and behaviors, HTTP requests/responses, server behaviors,... | |
3. Automating skills | |
Scripting: MS DOS bat scripting, MS Windows powershell scripting, Linux shell scripting (preferred) | |
Thinking of automation: Using Macro (MS Office macro, other applications macro), Using Regular expression | |
Tools used for performance testing is preferred | |
4. Testing tools: | |
Load testing tools: IBM Rational robot, IBM Rational performance tester, HP/Mercury LoadRunner, OpenSTA,... JMeter, soapUI , | |
Server monitoring tools: TOAD, MS Windows Performance meter, OpenNMS, Cacti, zabbix, graphite.... | |
Analyzing tools: MS excel/Google spreadsheet/OpenOffice spreadsheet, text manipulation tools (textpad, Notepad++, jEdit,...) | |
5. Testing skills | |
Good in performance testing, scripting, debuging, profiling, analyzing | |
III. NEEDED SKILLS FOR SECURITY TESTING | |
1. Require to smart, curious, to be passionate in security testing | |
2. Must have web application knowledge: HTML, javascript, browsers features and behaviors, HTTP requests/responses | |
3. Programming skills (preferred) | |
Application: application for linux/Windows, web applications is preferred | |
Language: java/C# is preferred, know well XML format | |
4. Tools used for debuging/profiling web application is preferred | |
Firebug, Fiddle, WebScarab, Wireshark , Chrome/Firefox developer toos... | |
WebScarab, Berretta, Nikto, WebInspect, Acunetix WVS, W3af , proxy tools ... | |
5. Testing skills | |
Good in web application manual testing/automation testing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment