Skip to content

Performance testing of the Simple Books REST API using JMeter and Java. Tested CRUD operations, measured response times, latency, and throughput under varying loads. Includes test plans, executed results, and performance reports to ensure API reliability and scalability.

Notifications You must be signed in to change notification settings

AhmedElian/Simple-Books-API-Performance-Project

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

📚 Simple Books API – Performance Testing Project

📖 Project Overview

  • This project demonstrates API performance testing for the Simple Books REST API using JMeter and Java.

  • It covers CRUD operations for books and clients, measures response time, latency, throughput, and validates API functionality under different loads.

  • Duration: 3 days

  • Team: 4 QAs

  • Methodology: Scrum (Sprint Planning, Daily Scrum, Sprint Review)

  • Scrum Meetings:

    • Sprint Planning: 2 hours on Day 1 — analyzed API endpoints, defined test scenarios, and assigned tasks.

    • Daily Scrum: 10 minutes daily — shared progress, discussed blockers.

    • Sprint Review: 1 hour on Day 3 — presented results, shared reports, and collected feedback.


🛠 API Details

  • Selected API: Simple Books API

  • Description: RESTful API for managing books and clients. Supports CRUD operations for books, including creation, retrieval, update, and deletion. Designed to handle multiple client requests while maintaining performance and stability.


🎯 Why Test Simple Books API?

  • Performance & Reliability: Ensure API responds correctly under varying loads.

  • Data Integrity: CRUD operations must behave as expected.

  • Scalability: API should handle multiple concurrent requests without failures.

  • Edge Case Handling: Validates large payloads, invalid data, and boundary conditions.


🔄 Workflows Covered

  • Create a new book or client

  • Retrieve book or client by ID / list

  • Update existing book or client

  • Delete book or client

  • Performance testing under concurrent user load

  • Boundary and edge case testing


📂 Project Phases

  • Phase 1: Preparation

    • Defined API endpoints and scenarios

    • Created Test Plan, Test Scenarios, and Test Cases

    • Prepared JMeter scripts and test data

  • Phase 2: Implementation

    • Built JMeter test scripts

    • Added assertions to validate API responses

    • Configured load, concurrency, and test parameters

  • Phase 3: Execution

    • Ran performance tests under various user loads

    • Monitored response time, latency, throughput, and error rates

    • Collected logs and metrics for analysis

  • Phase 4: Reporting & Closure

    • Documented test results with graphs and metrics

    • Logged performance issues and anomalies

    • Delivered Test Summary Report


🛠 Tools & Frameworks

  • JMeter: Load generation and performance testing

  • Excel / Google Sheets: Test cases, metrics recording

  • GitHub: Version control and collaboration


📦 Deliverables

  • SRS

  • Test Plan

  • Test Scenarios & Test Cases (15)

  • JMeter Test Scripts

  • Performance Test Results & Graphs

  • Defects / Observations Report

  • Test Summary Report

About

Performance testing of the Simple Books REST API using JMeter and Java. Tested CRUD operations, measured response times, latency, and throughput under varying loads. Includes test plans, executed results, and performance reports to ensure API reliability and scalability.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •