🏨 Hotel Booking Wiki

The Hotel Booking application is a multi-resource property management system designed for QA practice. It covers the full hospitality lifecycle — from adding properties and defining room types to creating bookings with dynamic pricing, updating booking statuses, and submitting guest reviews.

A unique feature is the QA Chaos Lab, which injects intentional failures into API responses to simulate real-world instability: network delays, data corruption, race conditions, and permission issues. This makes Hotel the ideal app for resilience and negative testing.

Key Characteristics

4 interconnected resource types: Properties → Room Types → Bookings → Reviews
Dynamic total amount calculation: price_per_night × rooms × nights
Booking statuses with strict lifecycle transitions
Reviews restricted to CHECKED_OUT bookings only
Chaos Lab with 4 chaos packs at configurable intensity (0–100%)
Data reset to template state via POST /api/hotel/reset
All endpoints require API key authentication

Quick Start

Step 1

Add Property

Name, city, country, star rating

→

Step 2

Add Room Type

Bed type, price, capacity, rooms

→

Step 3

Create Booking

Guest details, dates, guests/rooms

→

Step 4

Progress Status

PENDING → CONFIRMED → CHECKED_IN → CHECKED_OUT

→

Step 5

Submit Review

Only after CHECKED_OUT

Authentication: All API calls require Authorization: qac_live_<your_api_key> in the request header. Get your key from the Profile page.

UI Overview

The Hotel interface is a single-page application with four tabs: Properties, Room Types, Bookings, and Reviews. A hotel banner image appears at the top of each tab. The top navigation provides access to the QA Chaos Lab, API Docs, Data Viewer, and Profile.

Properties Tab

Contains an Add New Property form with fields: Property Name*, City*, Country*, Star Rating (1–5 dropdown), Address*, Postal Code, Phone, Email, Check-In Time (default 03:00 PM), Check-Out Time (default 11:00 AM), Description textarea, and Cancellation Policy textarea (default: "Free cancellation up to 24 hours before check-in").

Below the form: My Properties table with columns — Name, City, Country, Rating (star icons), Status (ACTIVE badge), and Actions (DELETE button in red).

Room Types Tab

Contains an Add Room Type form: Select Property* (dropdown), Room Type Name*, Bed Type* (Single/Double/Queen/King/Twin), Max Occupancy*, Room Size (sqm), Price Per Night ($)*, Total Rooms*, Description, Amenities (comma-separated, e.g. "WiFi, TV, AC, Mini Bar").

Below: Room Types table — Property, Room Type, Bed Type, Max Occupancy, Price/Night, Total Rooms, Status (AVAILABLE badge), Actions (DELETE).

Bookings Tab

Stats dashboard at top: Total Bookings, Pending, Confirmed, Checked In, Total Revenue (in dollars).

Create New Booking form: Property*, Room Type* (filtered by selected property), Guest Name*, Guest Email*, Guest Phone*, Check-In Date*, Check-Out Date*, Number of Guests*, Number of Rooms (default 1), Special Requests textarea.

All Bookings section with Filter by Status dropdown (All Statuses). Table columns: Confirmation #, Guest, Property, Room Type, Check-In, Check-Out, Guests, Total Amount, Status, Actions.

Reviews Tab

Guest Reviews table: Guest, Property, Rating, Comment, Date. The + ADD REVIEW button (top right) opens the review submission form. Reviews require a completed (CHECKED_OUT) booking.

Top Navigation

Item	Description
🎲 Chaos (cyan badge)	Opens the QA Chaos Lab modal — toggles chaos for the session
📖 API Docs	Links to Swagger UI with full API reference
🔍 Data Viewer	Read-only table view of all hotel data
← Profile	Returns to main profile/apps page
☀️ / 🌙	Dark/light theme toggle

QA Chaos Lab

The Chaos Lab is a unique testing feature that randomly injects failures into Hotel API responses. It is controlled per-user and does not affect other users. Click the 🎲 Chaos button in the top nav to open the modal.

Configuration

Chaos Session toggle — Enables/disables chaos for the current session
Intensity slider — 0% = never triggers, 100% = always triggers, default 50%
Random Seed — Enter the same seed to reproduce specific chaos scenarios

Pack A

Network Instability

Simulates network delays, timeouts, and connection issues. Returns 1xx, 5xx, and 503 errors for random requests.

Pack B

Data Validation Errors

Corrupts API responses: removes fields, breaks JSON structure, changes data types, injects null values.

Pack C

Race Conditions

Corrupts data BEFORE/AFTER one rule triggers: string→numbers swaps, drops fields, swaps values unexpectedly.

Pack D

Security & Permissions

Tests authentication boundaries, access control, permission escalation, and security edge cases.

QA note: When Chaos is active, normal API calls may return unexpected errors. Test your client's error handling, retry logic, and graceful degradation under chaos conditions.

Property Flow

Properties are the top-level resource. All other resources (room types, bookings, reviews) belong to a property. Properties can be active or inactive.

Required fields: name, address, city, country
Star rating must be between 1 and 5 (integer)
Default check-in time: 15:00:00, default check-out: 11:00:00
Deleting a property cascades down — room types, bookings, and reviews are also removed
Filter by is_active and city query params

Room Types Flow

Room types define the inventory under a property. They set the price, capacity, and availability used when creating bookings.

Required: property_id, name, max_occupancy, bed_type, price_per_night, total_rooms
Bed types: Single, Double, Queen, King, Twin
is_available flag — unavailable room types cannot be booked
Amenities passed as a comma-separated string in the UI, stored as an array
Validation: max_occupancy ≥ 1, price_per_night ≥ 0, total_rooms ≥ 1

Booking Flow

Bookings represent guest reservations. The total amount is auto-calculated and the confirmation number is auto-generated.

Booking Lifecycle

PENDING → CONFIRMED → CHECKED_IN → CHECKED_OUT

PENDING / CONFIRMED → CANCELLED PENDING / CONFIRMED → NO_SHOW

Business Rules

Check-out date must be strictly after check-in date
Number of guests must be ≥ 1, number of rooms ≥ 1
Room type must be is_available = true to book
Total amount = price_per_night × number_of_rooms × nights
Confirmation number format: HB20260414-XXXXXX (date + random)
Cancellation requires recording cancellation_reason (optional but tracked)

Review Flow

Guests can leave a review only after their booking reaches CHECKED_OUT status. Only one review per booking is permitted.

Required: booking_id, property_id, rating (1–5)
Optional sub-ratings: cleanliness_rating, service_rating, location_rating, value_rating
Submitting a review for a non-CHECKED_OUT booking returns 400
Duplicate reviews for the same booking return 400 (unique constraint)

API – Properties

Base path: /api/hotel/properties

POST /api/hotel/properties Create a new property

Field	Type	Required	Notes
`name`	string	required	Property name
`address`	string	required	Street address
`city`	string	required	City
`country`	string	required	Country
`star_rating`	integer	optional	1–5
`postal_code`	string	optional
`phone`	string	optional
`email`	string	optional
`check_in_time`	string	optional	Default: 15:00:00
`check_out_time`	string	optional	Default: 11:00:00
`description`	string	optional
`cancellation_policy`	string	optional	Default: "Free cancellation up to 24 hours before check-in"

Returns: 201 with created property object. 400 if required fields missing or star_rating out of range.

GET /api/hotel/properties List all properties

Query Param	Type	Notes
`is_active`	boolean	Filter by active/inactive
`city`	string	Case-insensitive partial match

Returns: 200 with array of properties, ordered by created_at DESC.

GET /api/hotel/properties/:id Get property by ID

Returns: 200 with property object. 404 if not found or not owned by the authenticated user.

PUT /api/hotel/properties/:id Update a property

Updatable fields: name, description, address, city, country, postal_code, phone, email, star_rating, check_in_time, check_out_time, cancellation_policy, is_active.

Returns 400 if no valid fields provided. Unknown fields are silently ignored.

DELETE /api/hotel/properties/:id Delete a property

Returns: 200 with deleted property. 404 if not found.

API – Room Types

Base path: /api/hotel/room-types

POST /api/hotel/room-types Add a room type to a property

Field	Type	Required	Notes
`property_id`	uuid	required	Must be owned by authenticated user
`name`	string	required	e.g. "Deluxe Suite"
`max_occupancy`	integer	required	≥ 1
`bed_type`	string	required	Single, Double, Queen, King, Twin
`price_per_night`	number	required	≥ 0
`total_rooms`	integer	required	≥ 1
`room_size_sqm`	number	optional
`description`	string	optional
`amenities`	array	optional	e.g. ["WiFi","TV","AC"]

GET /api/hotel/room-types List all room types

Query Param	Notes
`property_id`	Filter by property UUID
`is_available`	true/false

Ordered by price_per_night ASC.

GET /api/hotel/room-types/:id Get room type by ID

Returns: 200 with room type. 404 if not found or property not owned by authenticated user.

PUT /api/hotel/room-types/:id Update a room type

Updatable: name, description, max_occupancy, bed_type, room_size_sqm, amenities, price_per_night, total_rooms, images, is_available. Returns 400 if no valid fields provided.

DELETE /api/hotel/room-types/:id Delete a room type

Returns 200 with deleted room type object. 404 if not found.

GET /api/hotel/availability Check room availability for dates

Query Param	Required	Notes
`property_id`	required	UUID
`room_type_id`	required	UUID
`check_in_date`	required	YYYY-MM-DD
`check_out_date`	required	YYYY-MM-DD

API – Bookings

Base path: /api/hotel/bookings

POST /api/hotel/bookings Create a booking

Field	Type	Required	Notes
`property_id`	uuid	required
`room_type_id`	uuid	required	Must belong to property
`guest_name`	string	required
`guest_email`	string	required
`guest_phone`	string	required
`check_in_date`	date	required	YYYY-MM-DD
`check_out_date`	date	required	Must be after check-in
`number_of_guests`	integer	required	≥ 1
`number_of_rooms`	integer	optional	Default: 1
`special_requests`	string	optional

Total amount is auto-calculated: price_per_night × number_of_rooms × nights. Confirmation number auto-generated.

GET /api/hotel/bookings List all bookings

Query Param	Notes
`property_id`	Filter by property
`status`	PENDING, CONFIRMED, CHECKED_IN, CHECKED_OUT, CANCELLED, NO_SHOW
`check_in_date`	Filter bookings with check-in on or after this date
`check_out_date`	Filter bookings with check-out on or before this date

PATCH /api/hotel/bookings/:id/status Update booking status

Body: { "status": "CONFIRMED", "cancellation_reason": "..." }

Valid statuses: PENDING, CONFIRMED, CHECKED_IN, CHECKED_OUT, CANCELLED, NO_SHOW

Sets confirmed_at when status becomes CONFIRMED. Sets cancelled_at when status becomes CANCELLED.

DELETE /api/hotel/bookings/:id Delete a booking

Returns 200 with deleted booking object. 404 if not found.

POST /api/hotel/reset Reset all hotel data to template state

Deletes all user's hotel data and repopulates from template. Returns counts of deleted and created resources.

API – Reviews

Base path: /api/hotel/reviews

POST /api/hotel/reviews Submit a guest review

Field	Type	Required	Notes
`booking_id`	uuid	required	Booking must be CHECKED_OUT
`property_id`	uuid	required
`rating`	integer	required	1–5
`cleanliness_rating`	integer	optional	1–5
`service_rating`	integer	optional	1–5
`location_rating`	integer	optional	1–5
`value_rating`	integer	optional	1–5
`comment`	string	optional

Returns 400 if booking is not CHECKED_OUT or if a review already exists for the booking.

GET /api/hotel/reviews List all reviews

Query Param	Notes
`property_id`	Filter by property UUID

Ordered by created_at DESC. Includes guest name and property name in the response.

Test Cases

Properties

TC-PROP-001 Create property with all required fields Expected Pass

Send POST /api/hotel/properties with name, address, city, country

Response: 201 with property object containing generated id and is_active: true

TC-PROP-002 Create property with star_rating = 6 (out of range) Expected Fail

Send POST /api/hotel/properties with valid required fields and star_rating: 6

Response: 400 — star rating must be between 1 and 5

TC-PROP-003 Create property missing required field (no city) Expected Fail

Send POST /api/hotel/properties with name, address, country — omit city

Response: 400 — Name, address, city, and country are required

TC-PROP-004 Set property is_active to false via PUT Expected Pass

Create a property
PUT /api/hotel/properties/:id with { "is_active": false }
GET /api/hotel/properties?is_active=false

Returned list includes the deactivated property. GET with is_active=true excludes it.

TC-PROP-005 Update property with no valid fields Expected Fail

PUT /api/hotel/properties/:id with body { "unknown_field": "value" }

Response: 400 — No valid fields to update

Room Types

TC-ROOM-001 Create room type with price_per_night = 0 Expected Pass

POST /api/hotel/room-types with valid fields and price_per_night: 0

Response: 201 — zero price is allowed (free rooms)

TC-ROOM-002 Create room type with negative price Expected Fail

POST /api/hotel/room-types with price_per_night: -50

Response: 400 — Invalid values for max occupancy, price, or total rooms

TC-ROOM-003 Create room type for a property not owned by user Expected Fail

POST /api/hotel/room-types with a valid property_id that belongs to a different user

Response: 404 — Property not found

TC-ROOM-004 Mark room type as unavailable, then try booking it Expected Fail

PUT /api/hotel/room-types/:id with { "is_available": false }
POST /api/hotel/bookings referencing that room type

Response: 400 — Room type is not available for booking

Bookings

TC-BOOK-001 Create booking and verify total amount calculation Expected Pass

Create a room type with price_per_night: 100
POST booking with same-day dates spanning 3 nights, number_of_rooms: 2

Response: 201 — total_amount = 100 × 2 × 3 = 600

TC-BOOK-002 Create booking with check-out = check-in (same day) Expected Fail

POST /api/hotel/bookings with check_in_date = check_out_date

Response: 400 — Check-out date must be after check-in date

TC-BOOK-003 Create booking with check-out before check-in Expected Fail

POST booking where check_out_date < check_in_date

Response: 400 — Check-out date must be after check-in date

TC-BOOK-004 Progress booking through full lifecycle Expected Pass

Create booking → status: PENDING
PATCH status → CONFIRMED (confirmed_at is set)
PATCH status → CHECKED_IN
PATCH status → CHECKED_OUT

Each step returns 200 with updated status. After CHECKED_OUT, booking is eligible for a review.

TC-BOOK-005 Cancel booking and include cancellation_reason Expected Pass

PATCH /api/hotel/bookings/:id/status with { "status": "CANCELLED", "cancellation_reason": "Guest request" }

Response: 200 — cancelled_at timestamp set, cancellation_reason stored

TC-BOOK-006 Submit booking with invalid status value Expected Fail

PATCH /api/hotel/bookings/:id/status with { "status": "DONE" }

Response: 400 — Invalid status

Reviews

TC-REV-001 Submit review for a CHECKED_OUT booking Expected Pass

Complete full booking lifecycle to CHECKED_OUT
POST /api/hotel/reviews with booking_id, property_id, rating: 4

Response: 201 with review object

TC-REV-002 Submit review for a PENDING booking Expected Fail

Create a booking (status: PENDING)
POST /api/hotel/reviews with that booking_id

Response: 400 — Booking not found or not checked out yet

TC-REV-003 Submit duplicate review for same booking Expected Fail

Submit a successful review for a CHECKED_OUT booking
POST the same booking_id + property_id again

Response: 400 — Review already exists for this booking

TC-REV-004 Submit review with rating = 0 (below minimum) Expected Fail

POST /api/hotel/reviews with rating: 0 for a valid CHECKED_OUT booking

Response: 400 — Rating must be between 1 and 5

UI Test Cases

TC-UI-001 Add New Property form renders all required fields Expected Pass

Navigate to Hotel app → Properties tab
Verify form contains: Property Name*, City*, Country*, Star Rating dropdown, Address*, Postal Code, Phone, Email, Check-In Time, Check-Out Time, Description, Cancellation Policy

All fields visible. Required fields marked with *. Star Rating shows "Select" placeholder. Check-In defaults to 03:00 PM, Check-Out to 11:00 AM.

TC-UI-002 Submit Add Property form with empty required fields Expected Fail

Leave Property Name, City, Country, and Address blank
Click ADD PROPERTY

Error displayed. Property not added to the table below.

TC-UI-003 My Properties table shows correct columns and data Expected Pass

Add a property
Verify table shows: Name, City, Country, Rating (stars), Status (ACTIVE badge), Actions (DELETE)

Star rating renders as star icons (e.g. ★★★ for 3). Status shows green ACTIVE badge.

TC-UI-004 Room Types: Select Property dropdown populates from created properties Expected Pass

Add 2 properties
Navigate to Room Types tab
Click Select Property dropdown

Dropdown lists both created properties by name.

TC-UI-005 Room Types table shows AVAILABLE status badge Expected Pass

Add a room type
Verify the Room Types table row shows AVAILABLE badge in Status column

Green AVAILABLE badge displayed. Table shows Property, Room Type, Bed Type, Max Occupancy, Price/Night, Total Rooms, Status, Actions.

TC-UI-006 Bookings stats dashboard shows zero values initially Expected Pass

Navigate to Bookings tab with no bookings created

Stats bar shows: Total Bookings: 0, Pending: 0, Confirmed: 0, Checked In: 0, Total Revenue: $0.00

TC-UI-007 Create Booking: Room Type updates when Property changes Expected Pass

Select Property A in Create New Booking form
Note Room Type options
Change Property to Property B

Room Type dropdown updates to show only room types for the newly selected property.

TC-UI-008 Filter bookings by status in All Bookings section Expected Pass

Create bookings with different statuses
Use Filter by Status dropdown in All Bookings section
Select "CONFIRMED"

Table shows only CONFIRMED bookings. Selecting "All Statuses" shows all bookings again.

TC-UI-009 Reviews tab: Guest Reviews table is empty initially Expected Pass

Navigate to Reviews tab with no reviews submitted

Guest Reviews table shows column headers (Guest, Property, Rating, Comment, Date) but no rows. + ADD REVIEW button visible in top right.

TC-UI-010 QA Chaos Lab modal opens and closes correctly Expected Pass

Click 🎲 Chaos button in top nav
Verify modal opens with: session toggle, intensity slider, random seed input, 4 chaos pack checkboxes
Click X to close

Modal appears centered. All chaos packs (A, B, C, D) shown with descriptions. Closing returns to normal app state.

TC-UI-011 Chaos intensity slider accepts values 0–100% Expected Pass

Open Chaos modal
Drag intensity slider to 0%
Drag to 100%
Set to 50%

Slider moves smoothly. Label updates with the current percentage. Default shown as 50%.

TC-UI-012 DELETE property button removes it from table Expected Pass

Add a property
Click DELETE button in its table row
Confirm deletion prompt if shown

Property removed from My Properties table immediately. Row count decrements.

QA Tasks

Hands-on challenges designed for manual testing, API automation, and chaos resilience testing.

#1 Full Booking Lifecycle Manual

Create a property → add a room type → make a booking → progress it through PENDING → CONFIRMED → CHECKED_IN → CHECKED_OUT → submit a review. Verify the total amount calculation is correct at each step.

#2 Booking Date Boundary Testing Automation

Automate a suite of booking date edge cases: same-day check-out, check-out before check-in, 1-night stays, and multi-month stays. Assert correct 400/201 responses and validate calculated amounts.

#3 Chaos: Network Instability Resilience Chaos

Enable Chaos Pack A at 75% intensity. Perform a booking creation workflow and observe how many requests fail. Verify your client retries on 5xx errors and surfaces friendly error messages on timeout.

#4 Review Gate Enforcement Automation

Attempt to POST a review for bookings in each non-CHECKED_OUT status (PENDING, CONFIRMED, CHECKED_IN, CANCELLED, NO_SHOW). Verify all return 400. Only CHECKED_OUT allows a review.

#5 Star Rating Boundary Exploration Manual

Create properties with star_rating: 0, 1, 3, 5, and 6. Document which values succeed and which fail. Try updating an existing property's star rating to out-of-range values via PUT.

#6 Cross-User Isolation Test Automation

Use two different API keys. Create a property with User A. Attempt to create a room type under that property with User B's key. Document the response. Try to fetch User A's bookings with User B. Assert no data leaks across users.

#7 Chaos: Data Corruption Detection Chaos

Enable Pack B (Data Validation Errors) at 100% intensity. Run GET /api/hotel/properties and GET /api/hotel/bookings repeatedly. Document all response anomalies: missing fields, wrong types, broken JSON. Test whether your parser/client handles them gracefully.

#8 Room Availability and Booking Conflict Manual

Disable a room type via PUT (is_available: false), then attempt to book it. Restore it (is_available: true) and book again successfully. Use the availability check endpoint to query before booking.

#9 Reset Data and Verify Template State Manual

Delete all properties manually. Then call POST /api/hotel/reset. Verify the response reports created properties and room types. Check the Properties tab in UI and confirm template data is restored.

#10 Chaos: Reproduce Scenario with Seed Chaos

Enable chaos and note the Random Seed value displayed. Perform 5 API operations and note which ones failed. Reset the seed to the same value. Repeat the same 5 operations and verify the same failures occur — chaos is reproducible with the same seed.