How maro-z/restful-booker-performance-testing works
This repository is a JMeter performance test plan for the Restful Booker API. Its principal workflow authenticates, creates a booking from CSV data, retrieves it, and conditionally deletes it; the plan also applies pacing and a response-time assertion. The graph reflects only relationships documented in the README: no JMX source excerpt was provided to verify implementation details.
Main entry points: final4.jmx Test plan · booking_guests.csv Guest CSV data
Components 11
Test scenario
- Test plan
final4.jmx - Authenticate
final4.jmx - Create booking
final4.jmx - Guest CSV data
booking_guests.csv - Retrieve booking
final4.jmx - Conditional delete
final4.jmx
Test controls
- Throughput control
final4.jmx - Pacing timer
final4.jmx - Duration assertion
final4.jmx
Other components
- JMeter runner
- Restful Booker API
Connections 18
- JMeter runner → Test plan: runs
README.md - Test plan → Authenticate: executes first
README.md - Test plan → Create booking: executes next
README.md - Test plan → Retrieve booking: executes next
README.md - Test plan → Conditional delete: executes next
README.md - Authenticate → Restful Booker API: POST /auth
README.md - Authenticate → Create booking: passes token
README.md - Authenticate → Retrieve booking: passes token
README.md - Authenticate → Conditional delete: passes token
README.md - Guest CSV data → Create booking: provides names
README.md - Create booking → Restful Booker API: POST /booking
README.md - Create booking → Retrieve booking: passes booking ID
README.md - Create booking → Conditional delete: passes booking ID
README.md - Retrieve booking → Restful Booker API: GET booking
README.md - Throughput control → Conditional delete: limits to 25%
README.md - Conditional delete → Restful Booker API: DELETE booking
README.md - Pacing timer → Test plan: paces requests
README.md - Duration assertion → Test plan: checks duration
README.md