From 0cd3728c1075489223cace59a483a1aedea7372a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?NaveenKumar=20Namachivayam=20=E2=9A=A1?= Date: Tue, 4 Oct 2022 09:18:52 -0400 Subject: [PATCH] Add: Load and Performance Test (#2054) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Add: Load and Performance Test Signed-off-by: NaveenKumar Namachivayam ⚡ * Update content/roadmaps/113-qa/content/104-qa-non-functional-testing/100-load-and-performance-testing/readme.md Signed-off-by: NaveenKumar Namachivayam ⚡ Co-authored-by: Kamran Ahmed --- .../100-load-and-performance-testing/readme.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/113-qa/content/104-qa-non-functional-testing/100-load-and-performance-testing/readme.md b/content/roadmaps/113-qa/content/104-qa-non-functional-testing/100-load-and-performance-testing/readme.md index b529e575f..0470a746f 100644 --- a/content/roadmaps/113-qa/content/104-qa-non-functional-testing/100-load-and-performance-testing/readme.md +++ b/content/roadmaps/113-qa/content/104-qa-non-functional-testing/100-load-and-performance-testing/readme.md @@ -1 +1,15 @@ -# Load and performance testing \ No newline at end of file +# Load and Performance Testing + +Performance Testing is a subset of Performance Engineering. It is a process of evaluating a system’s behavior under various extreme conditions. The main intent of performance testing is to monitor and improve key performance indicators such as response time, throughput, memory, CPU utilization, and more. + +There are three objectives (three S) of Performance testing to observe and evaluate: `Speed`, `Scalability` and `Stability`. Following are the commonly used performance testing types, but not limited to: + +- Load Testing +- Stress Testing +- Spike Testing +- Endurance Testing +- Volume Testing +- Scalability Testing +- Capacity Testing + +Load Testing is one type of performance testing. It helps to evaluate the application under tests' behaviors such as response time, throughput, pass/fail transactions, and more under the normal workload. e.g., cart checkout response time is 500 milliseconds under typical business hours.