performance-testing

Getting started with performance-testing

Remarks#

This section provides an overview of what performance-testing is, and why a developer might want to use it.

It should also mention any large subjects within performance-testing, and link out to the related topics. Since the Documentation for performance-testing is new, you may need to create initial versions of those related topics.

Installation or Setup

Performance testing is a subject/process/testing methodology but not a tool to setup.

It includes the following core activities:

  1. Identify Test Environment
  2. Identify Performance Acceptance Criteria
  3. Plan and Design Tests
  4. Configure Test Environment
  5. Implement Test Design
  6. Execute Tests
  7. Analyze, Report, and Retest

The objective of performance testing is to validate the capacity and scalability of the deployed server.

Following are the key performance indicators:

  1. Availability - Uptime.
  2. Response Time
  3. Throughput
  4. Utilization (Server and Network)

References:

  1. Performance Testing Guidance for Web Applications

This modified text is an extract of the original Stack Overflow Documentation created by the contributors and released under CC BY-SA 3.0 This website is not affiliated with Stack Overflow