QA Portfolio — Booking.com Test Suite

A complete QA automation portfolio built on Booking.com using industry-standard practices: Gherkin BDD, Playwright (TypeScript), Cypress (JavaScript), and GitHub Actions CI/CD.

Tech Stack

Layer	Tool	Language
Test design & specification	Gherkin / Cucumber	—
E2E & API automation	Playwright	TypeScript
E2E & API automation	Cypress	JavaScript
DB-level validation	SQL	PostgreSQL
Lightweight API checks	cURL	Bash
CI/CD quality gates	GitHub Actions	YAML

Project Structure

tests/
├── manual/
│   └── features/
│       ├── api/                     # 11 API feature files
│       │   ├── 01_login_success.feature
│       │   ├── 02_login_failure.feature
│       │   ├── 03_search_city.feature
│       │   ├── 04_search_dates.feature
│       │   ├── 05_price_filter.feature
│       │   ├── 06_currency_conversion.feature
│       │   ├── 07_add_to_wishlist.feature
│       │   ├── 08_remove_from_wishlist.feature
│       │   ├── 09_view_details.feature
│       │   ├── 10_get_reviews.feature
│       │   └── 11_hotel_review_crud.feature   ← Full CRUD lifecycle
│       └── e2e/                     # 10 UI feature files
│           ├── booking.feature
│           ├── language_switch.feature
│           ├── currency_switch.feature
│           ├── search_filters.feature
│           ├── invalid_login.feature
│           ├── form_validation.feature
│           ├── bva_search_boundaries.feature  ← Boundary Value Analysis
│           ├── ep_login_credentials.feature   ← Equivalence Partitioning
│           ├── decision_table_search_filters.feature ← Decision Table
│           └── state_transition_booking_flow.feature ← State Transition
└── automation/
    ├── api/
    │   ├── playwright/              # Playwright API step definitions (TS)
    │   ├── cypress/                 # Cypress API step definitions (JS)
    │   ├── curl/                    # 10 cURL scripts with response validation
    │   └── sql/                     # 10 SQL queries (JOINs, CTEs, window fns)
    └── e2e/
        ├── playwright/
        │   ├── pages/               # Page Object Model (TypeScript)
        │   └── steps/               # Step definitions (TypeScript)
        ├── cypress/
        │   ├── pages/               # Page Object Model (JavaScript)
        │   └── steps/               # Step definitions (JavaScript)
        └── fixtures/
            └── world.ts             # Playwright browser/request lifecycle

Test Design Techniques

This project demonstrates six core ISTQB test design techniques:

Technique	Feature file	Coverage
Boundary Value Analysis	`bva_search_boundaries.feature`	Guest count (0–31), stay duration
Equivalence Partitioning	`ep_login_credentials.feature`	Email format classes, password classes
Decision Table	`decision_table_search_filters.feature`	Filter combinations → expected outcomes
State Transition	`state_transition_booking_flow.feature`	Full booking lifecycle state machine
Scenario Outline / Pairwise	`booking.feature`, `invalid_login.feature`	Multi-city search, multi-credential sets
Error Guessing	`02_login_failure.feature`, `form_validation.feature`	Invalid inputs, empty fields

Test Suites & Tags

Suite	Tag	When	Scope
Acceptance	`@Acceptance`	Every push to `main`	Core happy paths
Smoke	`@Smoke`	Nightly (sequential after Acceptance)	Key critical flows
Regression	`@Regression`	Nightly (sequential after Smoke)	Full coverage
Work In Progress	`@WIP`	Never in CI (excluded)	Features in development

API Coverage

#	Endpoint	Method	Test type
01	`/api/login`	POST	Auth success, token present
02	`/api/login`	POST	Auth failure, 401 response
03	`/api/hotels?city=`	GET	City search, result set validation
04	`/api/hotels?city=&checkin=&checkout=`	GET	Date-filtered availability
05	`/api/hotels?min_price=&max_price=`	GET	Price range filter
06	`/api/hotels?currency=`	GET	Currency conversion (USD/EUR/GBP)
07	`/api/wishlist`	POST	Create wishlist entry
08	`/api/wishlist/{id}`	DELETE	Remove wishlist entry
09	`/api/hotel/{id}`	GET	Hotel detail completeness
10	`/api/hotel/{id}/reviews`	GET	Review list with user & rating
11	`/api/hotel/{id}/reviews/{id}`	POST/GET/PUT/DELETE	Full CRUD lifecycle

Getting Started

Prerequisites

Node.js ≥ 20
npm ≥ 9

Setup

git clone https://github.com/yaoleshchuk/qa-pet-project.git
cd qa-pet-project
npm install
npx playwright install chromium --with-deps

Configure environment

cp .env.example .env

Edit .env with your test credentials (use a dedicated test account):

BASE_URL=https://www.booking.com
API_URL=https://www.booking.com
TEST_USER_EMAIL=your@email.com
TEST_USER_PASSWORD=yourpassword

Running Tests

Playwright + Cucumber (dry-run — step validation)

# Validate suite structure without a browser (fast, used in CI)
npm run test:pw:dry-run

# Run by suite (dry-run)
npm run test:pw:acceptance
npm run test:pw:smoke
npm run test:pw:regression

API Tests against Mock Server (real execution + Allure)

# 1. Start the mock API server (Express, port 3001)
npm run mock:start

# 2. In a separate terminal — run tests by suite
npm run test:api:acceptance   # @API + @Acceptance
npm run test:api:smoke        # @API + @Smoke
npm run test:api:regression   # @API + @Regression

# 3. Generate & open the Allure HTML report
npm run allure:generate
npm run allure:open

The mock server simulates all Booking.com API endpoints with realistic seed data, enabling fully deterministic test results without network access.

Cypress

# Interactive runner
npm run test:cypress:open

# Headless
npm run test:cypress:run
npm run test:cypress:acceptance
npm run test:cypress:smoke

cURL scripts (lightweight API smoke checks)

# Run a single script
BASE_URL=https://api.booking.com bash tests/automation/api/curl/01_login_success.sh

# Run all scripts
for f in tests/automation/api/curl/*.sh; do bash "$f" && echo; done

CI/CD (GitHub Actions)

Workflow	Trigger	Jobs
`on-main-acceptance.yml`	Push to `main`	`@Acceptance` dry-run
`manual-quality-gate.yml`	Manual dispatch	Selectable suite (acceptance / smoke / regression)
`nightly-full-run.yml`	Daily 00:00 UTC	All three suites sequentially (dry-run)
`api-mock-tests.yml`	Push to `main`, daily 01:30 UTC, manual dispatch	Real API tests against mock server → Allure report → GitHub Pages

The dry-run workflows validate step matching without a browser or live API. The mock-server workflow runs tests for real — against an Express mock server — and publishes an Allure HTML report to GitHub Pages.

To enable GitHub Pages: go to Settings → Pages → Source and set it to GitHub Actions.

Allure Reports

API tests produce a full Allure HTML report automatically on every CI run.

Live report

📊 View latest Allure report →

The report is published to GitHub Pages after every push to main and every nightly run via the api-mock-tests.yml workflow. It includes:

✅ Pass / ❌ Fail / ⚠️ Broken status per test
Full step-by-step execution log for each scenario
Tags, feature grouping, and suite breakdown
Duration timeline and statistics

How it works

Mock server starts (Express, port 3001)
        ↓
Cucumber runs API tests against mock server
        ↓
allure-cucumberjs writes results to allure-results/
        ↓
allure generate → allure-report/ (HTML)
        ↓
GitHub Pages deploys report → live URL

Run locally

# Terminal 1 — start mock server
npm run mock:start

# Terminal 2 — run tests and generate report
npm run test:api:acceptance
npm run test:api:smoke
npm run test:api:regression
npm run allure:generate
npm run allure:open        # opens browser automatically

SQL Queries

Located in tests/automation/api/sql/. Each query matches a specific test scenario and uses advanced SQL to validate data at the database layer:

Window functions: RANK(), ROW_NUMBER(), LAG(), PERCENT_RANK()
CTEs (Common Table Expressions) for multi-step logic
PERCENTILE_CONT for statistical assertions on review ratings
STRING_AGG for amenity list validation
Conditional aggregation with SUM(CASE WHEN … END)
Date overlap logic for availability validation

Built with ☕ by Yaroslav Oleshchuk

Name		Name	Last commit message	Last commit date
Latest commit History 29 Commits
.github/workflows		.github/workflows
mock-server		mock-server
tests		tests
.env.example		.env.example
.gitignore		.gitignore
README.md		README.md
cucumber.js		cucumber.js
cypress.config.js		cypress.config.js
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

QA Portfolio — Booking.com Test Suite

Tech Stack

Project Structure

Test Design Techniques

Test Suites & Tags

API Coverage

Getting Started

Prerequisites

Setup

Configure environment

Running Tests

Playwright + Cucumber (dry-run — step validation)

API Tests against Mock Server (real execution + Allure)

Cypress

cURL scripts (lightweight API smoke checks)

CI/CD (GitHub Actions)

Allure Reports

Live report

How it works

Run locally

SQL Queries

About

Uh oh!

Releases

Packages

Uh oh!

Contributors

Uh oh!

Languages

Folders and files

Latest commit

History

Repository files navigation

QA Portfolio — Booking.com Test Suite

Tech Stack

Project Structure

Test Design Techniques

Test Suites & Tags

API Coverage

Getting Started

Prerequisites

Setup

Configure environment

Running Tests

Playwright + Cucumber (dry-run — step validation)

API Tests against Mock Server (real execution + Allure)

Cypress

cURL scripts (lightweight API smoke checks)

CI/CD (GitHub Actions)

Allure Reports

Live report

How it works

Run locally

SQL Queries

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages