Scribd
Upload
2 views6 pages

Test Plan Documentation

The test plan aims to evaluate the performance of the Reqres REST API under a load of 100 concurrent users for 15 minutes, focusing on response times, throughput, and identifying bottlenecks. It includes performance testing for the Create API and List Users API, with key metrics such as average response time below 2 seconds and throughput of at least 100 requests per second. The testing will be conducted using Apache JMeter, with specific execution steps and assumptions outlined for successful performance evaluation.

Uploaded by

mayarmohamedwork1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views6 pages

Test Plan Documentation

The test plan aims to evaluate the performance of the Reqres REST API under a load of 100 concurrent users for 15 minutes, focusing on response times, throughput, and identifying bottlenecks. It includes performance testing for the Create API and List Users API, with key metrics such as average response time below 2 seconds and throughput of at least 100 requests per second. The testing will be conducted using Apache JMeter, with specific execution steps and assumptions outlined for successful performance evaluation.

Uploaded by

mayarmohamedwork1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

“ Test Plan documentation “

The purpose of this test plan is to evaluate the


performance of the Reqres REST API under a concurrent
user load of 100 users for a duration of 15 minutes. The
focus is to ensure the APIs meet the specified
performance criteria.

Objective

The primary objective is to:


• Assess the API’s ability to handle 100 concurrent
users.
• Measure response times, throughput, and error
rates.
• Identify performance bottlenecks or failure
points.
Scope

In Scope
• Performance testing of the following APIs:
1. Create API (POST /api/users)
2. List Users API (GET /api/users)

Out of Scope
• Functional testing of APIs.

Test Scenarios

Scenario 1: Create a User


• API Endpoint: POST /api/users
• Success Criteria: Response code 201 (Created) with
valid user details in the response body.

Scenario 2: List Users


• API Endpoint: GET /api/users
• Success Criteria: Response code 200 (OK) with a
valid user list in the response body.

Performance Metrics

Key Metrics
1. Response Time:
• Average response time should be below 2
seconds.
• 95th percentile response time should not
exceed 3 seconds.
2. Throughput:
• System should handle at least 100 requests per
second under load

Test Duration:
• Ramp-up Time: 60 seconds.
• Steady-State Duration: 15 minutes.
Tools and Environment

Tools Used
• Performance Testing Tool: Apache JMeter (v5.6
or later).
• Monitoring Tools: JMeter listeners (Summary
Report, Aggregate Report).

Environment Details
• API URL: https://reqres.in/
• Network Conditions: Standard internet
connection.

Test Data

Test Data for Create API


• Payloads with varied name and job values.
Test Execution Steps

Setup JMeter Test Plan


• Configure a Thread Group with 100 users, 60
seconds ramp-up, and 15-minute duration.
• Add HTTP Request Samplers for the POST
/api/users and GET /api/users endpoints.

Add Listeners
• Use Summary Report, Aggregate
Report,Response time graph and View Results Tree
listeners to capture performance metrics.

Execute Test
• Run the test plan and monitor performance in
real-time.

Analyze Results
• Review JMeter reports for response times,
throughput, and error rates.
Assumptions:
• Reqres API server is stable and capable of
handling the expected load.
• No significant changes occur in the API
endpoints during testing.

You might also like