How girishgktester/playwright_framework works
Project type and purpose
• This is a Playwright-based end-to-end test automation framework (Node.js) for e-commerce sites (dev: automationexercise.com, qa: demo.nopcommerce.com).
• Its goal is to provide a scalable, POM-driven test suite with environment management, data-driven tests, custom fixtures, reports, screenshots and CI/CD integration.
File structure
• Top-level modules:
• configs/ (dev, qa, stage + loader) – environment settings
• Data/ (FakerTestData.js, testData.json) – data generation & static JSON
• pages/ – Page Object Model classes (Home, Cart, Login, Search, etc.)
• tests/ – test specs invoking POM classes
• utils/ – common helpers (Hooks, Pageutils, constants, pageFactory, fixtures)
• playwright.config.js + test-runner.js – Playwright runner entry points
• .github/workflows/playwright-tests.yml – CI pipeline
• playwright-report/, screenshots/ – output artifacts
Key architecture notes from README
• Playwright Test Runner with parallel & cross-browser support
• Page Object Model + Page Factory
• Custom Playwright fixtures via test.extend
• Tag-based filtering, screenshot/video capture
• Environment loader using cross-env, dotenv, minimist
• CI via GitHub Actions