nopCommerce QA

Appearance

nopCommerce AutomationA Playwright test framework

Nine features, 34 tests, Page Object Model, and a real fight with Cloudflare.

How to Run
Getting Past Cloudflare
GitHub
nopCommerce and Playwright
🧱

Page Object Model

Selectors and actions live in page objects. The specs only say what to check, never how to find a button.

🎯

Pass, Fail, Edge

Every feature has a happy path, a negative case, and a boundary case. Several are data-driven from JSON.

🔁

Three checkout journeys

The full buy flow as a guest, as a logged-in user, and registering then buying in one session.

🛡️

Gets past Cloudflare

Handles the headless block and the Rocket Loader trick that makes clicks quietly do nothing.

⚡

API-assisted setup

Accounts are created by posting the form directly, then the feature is checked through the UI.

📊

Two reports

The built-in Playwright HTML report, plus the Pulse dashboard with trends across runs.

The short version ​

A Playwright and TypeScript test framework for the nopCommerce demo store. It covers nine features in 34 tests, checks the happy paths along with the ways things should break, and is built to hold up against a live site that Cloudflare actively guards.

It's split into two layers on purpose: the framework (page objects, fixtures, the data layer) is reusable scaffolding with no tests in it, and the suite is the feature specs plus three end-to-end checkout journeys.

By the numbers ​

Features9 (8 core + an end-to-end checkout)
Tests34 (Pass / Fail / Edge, several data-driven)
Page objects9 (BasePage + one per feature)
ReportingPlaywright HTML + Pulse (with trends)
On failurescreenshot, trace, and video
Proof34/34 even with --retries=0

Guides

Assignment deliverables

Built with Playwright + TypeScript · Page Object Model

nopCommerce demo-store automation