Nearly all performance testing is based on protocol simulation. This can be a neat, manageable, efficient way to performance test. Notably most tools in this market have the capability to performance test HTTP based applications. Some tools make a dogs dinner of script creation (usually open source), some are elegant & effective (usually commercial), and some hide everything under the covers including errors & mistakes etc and take a script-less approach (also usually commercial and in my view always best avoided).
HTTP lends itself very well to protocol level testing and most enterprise applications will use HTTP in some form or another. Of course not all applications use HTTP, there are still many that use other protocols such as ODBC, SQLNet, RMI and more. There are tools that can capture these protocols I can think of at least three, however in my experience the parameterisation of these scripts can be a daunting task for even the most seasoned automation expert. It can be time consuming, require expensive specialists and can fail. Also if the application is re-written, then the script often has to be too, causing further expense.
1.REQUIREMENT PHASE
Requirement Study
• Project Initiation
• Analyzing Test Goals and Objective
• Determining test scope
• Analyzing HW and SW
requirements.
• Test Initiation Checklist
2.PLANNING PHASE
• Test Plan, Test strategies.
• Selection of testing tools.
Generating Test Scenarios
/Scripts.
• Reviewing the test documents
and Base lining.
• Test Readiness Review
3.ENVIRONMENTAL SETUP
• Set up the environment as per
the requirement
• Installation of OS and software
and testing tools
• Test readiness review.
4.EXECUTION PHASE
• Performance Test Scenario / Script
Execution.
• Collect the Data.
• Analyze the Data.
• Problem Investigation like bottlenecks
(memory, disk, processor, process,
cache, network, etc.) resource usage
like (memory, CPU, network, etc.,)
• Generate the Performance analysis
reports containing all performance
attributes of the application.
• Create Recommendation report based
on the analysis.
• Repeat the above test for the new
build received from client after fixing
the bugs and implementing the
recommendations
5.COMPLETION PHASE
• Performance
• Test Report Generation
• Updating test documents
• Post implementation review
• Project completion checklist
Recent Activity in Forums
 | Lisa posted a new forum topic Regression Testing ? in Regression Testing |
| Lisa replied to forum topic Test plan and Test Strategy in Black Box Testing |
| Lisa replied to forum topic Test plan and Test Strategy in Black Box Testing |
| Netra posted a new forum topic How to decidePriority and Serverity in Black Box Testing |
| Shilpa posted a new forum topic High Level Scenarios for Coffee vending machine in Manual Testing |
| Atul posted a new forum topic For which ISTQB Advanced level exam shoud I appear? in Testing Certification - General |
| Netra posted a new forum topic Can 2 or more than 2 bugs have the same Test case ID in System Testing |
| Netra posted a new forum topic Involvement of developers/testers in testing process in Manual Testing |
| Netra posted a new forum topic How to determine defect type in the defect report in Manual Testing |
| Sumanth replied to forum topic TestLink the Open Source Test Management Tool in Test Management |