160 likes | 766 Views
Performance Testing as a Service using jMeter. Performance Testing Process Steps. Completion of Testing Engagement Form Completion of Test Planning Questionnaire Test Planning Session Development of Performance Test Plan Development of Automated Test Scripts in pre-production
E N D
Performance Testing Process Steps • Completion of Testing Engagement Form • Completion of Test Planning Questionnaire • Test Planning Session • Development of Performance Test Plan • Development of Automated Test Scripts in pre-production • Execution of Automated Test Scripts • Identification of Performance Issues from test executions • Resolution of Performance Issues • Development of Test Summary Report
1 week • Engagement Form • Design Review Engagement 1 week • Test Plan • Pre-Prod Review • MPC Schedule Planning 1 week • Script Writing Scripting • Test Results • Production Review 3 weeks Test Execution 1 week • Summary Test Report • Post Implementation Review Test Reporting Performance Testing Process - Sample Timeline • The timelines will be tailored based on the complexity of the project and availability of the resources
Different Tests that are conducted • Sample Metrics collected : • Transaction Performance Summary • Transaction Response Time – Average • Web Hits Per Second • Web Server Throughput • Average Load
Break Point Testing - Sample Break Point Testing (85 users – Break Point) Users Running: 85 Run time: 4 minutes Response time: > 7 sec Passed Transactions: 2354 Failed Transactions: 16 Error Rate: 0.67% Hits/second: 33 Queries/Minute: 588 CPU Utilization, Memory Utilization: Not Applicable for the testing of the Break point for queries
Fail-Over Testing • Criteria: • Durability testing, also known as failover testing in other environments, is used to verify that the application continues to operate properly even when primary infrastructure and application, global, and external components fail. Furthermore, the application must continue to operate under load after the failure for the specified time period. Less than 1% is considered a passing result. • Results: • Web/app hard failover (shutdown server) • Recovered in 15 second timeframe • Response times: 0.08-6.134 seconds • Errors: 767 (.4%) • Web/App soft failover (failover server software) • Recovered in 15 second timeframe • Response times: 0.34-4.6 seconds • Errors: 289 (.005%) • Database soft failover (Failover to secondary node) • Recovered in 60 second timeframe • Response times: 038-4.6 seconds • Errors: 294 (.005%) Failover Testing - Sample