Skip to content

Repository files navigation

πŸš€ Playwright Automation Framework

Enterprise-Ready | Smart Utilities | Data-Driven | Cross-Browser | Mobile Web

A scalable, reusable, and enterprise-ready Playwright Automation Framework designed for modern web and mobile browser automation.

Built with clean architecture, reusable utilities, smart execution features, environment management, cross-browser testing, and browser-based mobile automation.

⭐ If you like this project, don't forget to Star this repository!


πŸ“– Overview

This framework is built following enterprise automation best practices with a focus on:

  • Maintainability
  • Scalability
  • Execution stability
  • Test data management
  • Reusable components
  • Detailed reporting
  • Environment management
  • Cross-browser execution
  • Mobile web automation
  • CI/CD readiness

It helps teams build reliable Playwright automation by providing reusable utilities, environment management, environment-aware test data, custom fixtures, smart execution helpers, centralized assertions, organized artifacts, Allure reporting, email reporting, and modular project architecture.

The framework is designed to support both day-to-day automation execution and long-term framework scalability.


πŸš€ What's New in v1.2

  • βœ… Custom Playwright Fixtures
  • βœ… Environment-Aware Test Data Management
  • βœ… Allure Reporting
  • βœ… Allure Environment Information
  • βœ… Allure History & Trends
  • βœ… Soft Assertion Support
  • βœ… Email Execution Reporting
  • βœ… Automatic Report ZIP Generation
  • βœ… Allure Report Packaging
  • βœ… Playwright HTML Report Packaging
  • βœ… Screenshots, Videos & Trace Attachments
  • βœ… Global Setup & Teardown Reporting Integration
  • βœ… Improved Reporting Architecture

✨ Features

πŸ—οΈ Framework

  • βœ… Page Object Model (POM)
  • βœ… Modular Architecture
  • βœ… Custom Playwright Fixtures
  • βœ… Cross Browser Testing
  • βœ… Browser-Based Mobile Testing
  • βœ… Parallel Execution
  • βœ… Excel Data-Driven Framework
  • βœ… Environment-Aware Test Data
  • βœ… Multi-Environment Support
  • βœ… Reusable Utilities
  • βœ… Centralized Configuration

⚑ Smart Execution

  • βœ… Smart Click Utility
  • βœ… Smart Fill Utility
  • βœ… Smart Wait Utility
  • βœ… Generic Retry Utility
  • βœ… Assertion Utility
  • βœ… Soft Assertion Support
  • βœ… Execution Dashboard
  • βœ… Environment Management
  • βœ… Test Data Management

πŸ› οΈ Utilities

  • βœ… Excel Utility
  • βœ… Screenshot Utility
  • βœ… Download Utility
  • βœ… Faker Utility
  • βœ… Date & Time Utility
  • βœ… Common Utility
  • βœ… Assertion Utility
  • βœ… Environment Utility
  • βœ… Retry Utility
  • βœ… Wait Utility

πŸ“Š Reporting

  • βœ… HTML Report
  • βœ… Allure Report
  • βœ… Allure Environment
  • βœ… Allure History
  • βœ… Allure Trends
  • βœ… Execution Summary
  • βœ… Email Reporting
  • βœ… Automatic Report Packaging
  • βœ… Screenshots
  • βœ… Videos
  • βœ… Playwright Traces
  • βœ… Test Attachments
  • βœ… Smart Artifact Management

🌍 Environment Management

Execute the same test suite across multiple environments without changing test code.

Supported Environments

config
β”‚
└── environment
    β”œβ”€β”€ dev.env
    β”œβ”€β”€ uat.env
    β”œβ”€β”€ pre-prod.env
    └── prod.env

Run Tests

npm run uat
npm run preprod
npm run prod

Simply switch the command.

No test code changes are required.

The framework loads the corresponding environment configuration and uses the environment-specific Base URL and configuration during execution.


πŸ—ƒοΈ Environment-Aware Test Data

The framework includes an environment-aware test data management layer.

Environment switching is not limited to changing the application URL.

The framework also provides a structured approach for handling test data according to the selected environment.

Example

Environment
β”‚
β”œβ”€β”€ DEV
β”‚   └── DEV Test Data
β”‚
β”œβ”€β”€ UAT
β”‚   └── UAT Test Data
β”‚
β”œβ”€β”€ PRE-PROD
β”‚   └── PRE-PROD Test Data
β”‚
└── PROD
    └── PROD Test Data

This approach helps maintain separation between:

  • Application Configuration
  • Environment Configuration
  • Test Data
  • Test Implementation

The same automation test can therefore be executed across different environments without modifying the actual test implementation.


🧩 Custom Playwright Fixtures

Custom Playwright Fixtures have been integrated into the framework to centralize reusable test dependencies and setup logic.

Fixtures help reduce repeated setup code and provide a cleaner way to manage framework-level dependencies.

Benefits

  • Reusable test context
  • Reduced duplicate setup
  • Cleaner test cases
  • Centralized dependencies
  • Better maintainability
  • Easier framework extension
  • Consistent test initialization

Example

test('Login Test', async ({ page }) => {

    // Test implementation

});

Framework-level setup and reusable dependencies can be handled through fixtures instead of repeating setup logic across individual tests.


πŸ“Š Execution Dashboard

Every execution automatically displays:

  • Framework Version
  • Environment
  • Base URL
  • Browser
  • Execution Mode
  • Workers
  • Platform
  • Operating System
  • Node Version
  • Execution Start Time

Example

══════════════════════════════════════════════════════════════

πŸš€ Playwright Automation Framework

Framework Version : v1.2.0

Environment       : UAT

Base URL          : Environment Base URL

Browser           : Chromium

Execution Mode    : Parallel

Workers           : 4

Platform          : Windows

Operating System  : Windows

Node Version      : v22.x

Started At        : 30-Jul-2026

══════════════════════════════════════════════════════════════

The dashboard provides immediate visibility into the execution context before the test suite starts.


⚑ Smart Utilities

The framework includes reusable smart utilities designed to improve execution stability and reduce repetitive automation code.


πŸ–±οΈ Smart Click

await smartClick(page.locator("#login"));

Automatically:

  • Waits for visibility
  • Scrolls into view
  • Performs the click
  • Retries on failure
  • Provides execution logs

✍️ Smart Fill

await smartFill(username, "Admin");

Automatically:

  • Waits until editable
  • Clears existing value
  • Enters data
  • Verifies entered value
  • Retries if required
  • Provides execution logs

⏳ Smart Wait

await waitForPageReady(page);

Handles common page readiness conditions such as:

  • DOM Loaded
  • Network Idle
  • Loader Disappearance
  • Spinner Completion

πŸ§ͺ Assertion Utility

Instead of:

await expect(locator).toBeVisible();

Use:

await Assertion.assertVisible(locator);

Supports:

  • Element Assertions
  • Page Assertions
  • URL Assertions
  • Text Assertions
  • Count Assertions
  • API Assertions
  • Generic Assertions
  • Soft Assertions

The centralized assertion layer keeps validation logic consistent across the framework.


🌐 Supported Browsers

Browser Supported
Chromium βœ…
Chrome βœ…
Firefox βœ…
WebKit βœ…
Mobile Chrome βœ…
Mobile Safari βœ…

πŸ“‚ Framework Structure

Playwright_Automation
β”‚
β”œβ”€β”€ config
β”‚   β”‚
β”‚   β”œβ”€β”€ environment
β”‚   β”‚   β”œβ”€β”€ dev.env
β”‚   β”‚   β”œβ”€β”€ uat.env
β”‚   β”‚   β”œβ”€β”€ pre-prod.env
β”‚   β”‚   └── prod.env
β”‚   β”‚
β”‚   └── executionConfig.js
β”‚
β”œβ”€β”€ pages
β”‚
β”œβ”€β”€ tests
β”‚
β”œβ”€β”€ testData
β”‚
β”œβ”€β”€ fixtures
β”‚
β”œβ”€β”€ utilities
β”‚   β”œβ”€β”€ assertionUtil.js
β”‚   β”œβ”€β”€ clickUtil.js
β”‚   β”œβ”€β”€ dashboardUtil.js
β”‚   β”œβ”€β”€ downloadUtil.js
β”‚   β”œβ”€β”€ environmentUtil.js
β”‚   β”œβ”€β”€ excelUtil.js
β”‚   β”œβ”€β”€ fakerUtil.js
β”‚   β”œβ”€β”€ fillUtil.js
β”‚   β”œβ”€β”€ retryUtil.js
β”‚   β”œβ”€β”€ screenshotUtil.js
β”‚   └── waitUtil.js
β”‚
β”œβ”€β”€ reporting
β”‚   β”‚
β”‚   β”œβ”€β”€ allure
β”‚   β”‚   └── environmentWriter.js
β”‚   β”‚
β”‚   β”œβ”€β”€ email
β”‚   β”‚   β”œβ”€β”€ executionSummary.js
β”‚   β”‚   └── emailUtil.js
β”‚   β”‚
β”‚   └── zip
β”‚       └── zipReport.js
β”‚
β”œβ”€β”€ reports
β”œβ”€β”€ screenshots
β”œβ”€β”€ downloads
β”œβ”€β”€ allure-results
β”œβ”€β”€ allure-report
β”œβ”€β”€ playwright-report
β”œβ”€β”€ test-results
β”œβ”€β”€ global-setup.js
β”œβ”€β”€ global-teardown.js
β”œβ”€β”€ playwright.config.js
└── package.json

πŸ“Š Reporting

The framework provides multiple reporting layers for better execution visibility.

Automatically generates:

  • HTML Report
  • Allure Report
  • Execution Summary
  • Passed Test Cases
  • Failed Test Cases
  • Skipped Test Cases
  • Execution Duration
  • Screenshots
  • Videos
  • Playwright Traces
  • Test Attachments
  • Allure Environment Information
  • Allure History
  • Allure Trends
  • Organized Artifacts
  • Email Execution Report

πŸ“ˆ Allure Reporting

The framework integrates Allure Reporting for detailed execution analysis.

Allure provides:

  • Test Execution Summary
  • Passed Tests
  • Failed Tests
  • Skipped Tests
  • Test Duration
  • Test Details
  • Test Steps
  • Screenshots
  • Videos
  • Trace Information
  • Attachments
  • Environment Information
  • Categories
  • History
  • Trends

Generate Allure Report

allure generate allure-results --clean -o allure-report

Open Allure Report

allure open allure-report

Check Allure Version

npx allure --version

🌍 Allure Environment

The framework automatically provides execution environment information to the Allure report.

Environment information includes:

  • Framework Version
  • Test Environment
  • Browser
  • Operating System
  • Platform
  • Node Version
  • Base URL

This provides better visibility into where and how the test execution was performed.


πŸ“Š Allure History & Trends

Allure history and trend information is maintained across executions.

The report provides trend information such as:

  • Test Execution History
  • Duration Trends
  • Retry Trends
  • Category Trends

This allows teams to analyze execution stability and test behavior across multiple runs.


πŸ“§ Email Reporting

The framework includes automated email execution reporting.

The email report generates a professional HTML execution summary.

The report can include:

  • Execution Environment
  • Total Tests
  • Passed Tests
  • Failed Tests
  • Skipped Tests
  • Execution Duration
  • Execution Status
  • Test Summary
  • Report Attachments

Example

════════════════════════════════════════════

πŸš€ Playwright Automation Execution Summary

Environment : UAT

Total Tests : 10

Passed      : 8

Failed      : 1

Skipped     : 1

Execution Status : COMPLETED

════════════════════════════════════════════

πŸ“¦ Automatic Report Packaging

The framework automatically packages execution reports into ZIP files.

Generated Reports

reports
β”‚
β”œβ”€β”€ allure-report.zip
β”‚
└── playwright-report.zip

The generated ZIP files can be attached to the execution email.

This makes it easier to share complete execution results with:

  • QA Teams
  • Developers
  • Managers
  • Clients
  • CI/CD Stakeholders

πŸ“ Smart Artifact Management

Each execution automatically manages:

Execution
β”‚
β”œβ”€β”€ Reports
β”œβ”€β”€ Screenshots
β”œβ”€β”€ Downloads
└── Artifacts

Benefits

  • No overwritten reports
  • No mixed screenshots
  • Organized execution artifacts
  • Easier failure investigation
  • Easier report sharing

πŸ”„ Reporting Workflow

                          Test Execution
                               β”‚
                               β–Ό
                       Execution Dashboard
                               β”‚
                               β–Ό
                         Playwright Tests
                               β”‚
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
              β”‚                β”‚                 β”‚
              β–Ό                β–Ό                 β–Ό
        Screenshots          Videos            Traces
              β”‚                β”‚                 β”‚
              β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β–Ό
                         Test Results
                               β”‚
                               β–Ό
                         Allure Results
                               β”‚
                               β–Ό
                          Allure Report
                               β”‚
                               β–Ό
                       Report Packaging
                               β”‚
                               β–Ό
                        Email Reporting

πŸ“± Mobile Testing

Supports browser-based mobile automation using Playwright Device Emulation.

Features

  • Responsive Testing
  • Mobile Scroll Utility
  • Touch Gestures
  • Mobile Viewports
  • Cross Device Validation
  • Mobile Browser Testing

πŸš€ Parallel Execution

Supports:

  • Multiple Workers
  • Stable Parallel Execution
  • Independent Test Execution
  • Faster Test Execution
  • Cross Browser Execution
  • Organized Test Artifacts

πŸ“Š Data-Driven Testing

The framework supports Excel-based data-driven testing.

Excel utilities can be used for:

  • Test Data Management
  • Multiple Test Combinations
  • Parameterized Execution
  • Data-Driven Test Cases
  • Environment-Specific Test Data

Execution Flow

Excel Test Data
      β”‚
      β–Ό
Test Data Utility
      β”‚
      β–Ό
Test Case
      β”‚
      β–Ό
Playwright Execution

🎲 Faker Utility

The framework includes Faker-based dynamic test data generation.

It can be used for generating dynamic values such as:

  • Names
  • Mobile Numbers
  • Email Addresses
  • Random Values
  • Test Data

This reduces dependency on hardcoded test values.


πŸ› οΈ Utility Layer

The framework contains reusable utilities for common automation requirements.

Utilities Include

  • Assertion Utility
  • Click Utility
  • Fill Utility
  • Wait Utility
  • Retry Utility
  • Screenshot Utility
  • Download Utility
  • Excel Utility
  • Faker Utility
  • Environment Utility
  • Dashboard Utility
  • Common Utility

The utility layer helps reduce duplicate automation code and improves maintainability.


πŸ“· Framework Screenshots

Framework Structure

images/framework-structure.png

Execution Dashboard

images/dashboard.png

HTML Report

images/html-report.png

Allure Report

images/allure-report.png

Email Report

images/email-report.png

Artifacts

images/artifacts.png

πŸš€ Getting Started

Prerequisites

Make sure the following are installed:

  • Node.js
  • npm
  • Git
  • Playwright
  • Allure CLI

Clone Repository

git clone https://github.com/mrpathak20/Playwright-Automation-Framework.git

Navigate to Project

cd Playwright-Automation-Framework

Install Dependencies

npm install

Install Playwright Browsers

npx playwright install

▢️ Run Tests

Run All Tests

npx playwright test

Run Tests in Headed Mode

npx playwright test --headed

Run Specific Test

npx playwright test tests/example.spec.js

Run UAT

npm run uat

Run Pre-Production

npm run preprod

Run Production

npm run prod

πŸ“ˆ Allure Commands

Check Allure Version

npx allure --version

Generate Allure Report

allure generate allure-results --clean -o allure-report

Open Allure Report

allure open allure-report

πŸ“Š Playwright HTML Report

Open the Playwright HTML report:

npx playwright show-report

The Playwright report provides:

  • Test Execution Summary
  • Passed Tests
  • Failed Tests
  • Test Duration
  • Screenshots
  • Videos
  • Trace Viewer
  • Test Details

πŸ“§ Email Configuration

Email credentials should be managed through environment variables.

Example

EMAIL_FROM=your-email@example.com
EMAIL_PASSWORD=your-email-password
EMAIL_TO=recipient@example.com

Do not commit actual credentials to GitHub.

Recommended approaches include:

  • Environment Variables
  • GitHub Actions Secrets
  • Jenkins Credentials
  • Azure DevOps Variables
  • CI/CD Secret Management

πŸ” Environment & Credentials

Environment files containing credentials or sensitive information should not be committed to GitHub.

Sensitive information such as:

  • Usernames
  • Passwords
  • Email Credentials
  • API Credentials
  • Access Tokens

should be managed using environment variables or CI/CD secret management.


πŸ”„ Global Setup & Teardown

The framework uses global setup and teardown processes for framework-level execution tasks.

Global Setup

Global setup can be used for:

  • Framework initialization
  • Reporting folder preparation
  • Environment initialization
  • Execution preparation

Global Teardown

Global teardown can be used for:

  • Allure report generation
  • Report processing
  • Execution cleanup
  • Final reporting operations

This provides a centralized lifecycle for framework execution.


πŸš€ CI/CD Ready

The framework is structured for integration with:

  • GitHub Actions
  • Jenkins
  • Azure DevOps
  • GitLab CI

Execution reports and artifacts can be published as part of CI/CD execution.

The reporting architecture also allows execution summaries and reports to be distributed through email.


πŸ—οΈ Enterprise Architecture

The framework follows a modular architecture:

                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚     Test Cases      β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                β”‚
                                β–Ό
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚   Custom Fixtures   β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                β”‚
                β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                β–Ό               β–Ό               β–Ό
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚ Page Objects β”‚ β”‚ Test Data  β”‚ β”‚  Utilities   β”‚
        β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜
               β”‚               β”‚               β”‚
               β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β–Ό
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚ Playwright Engine   β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                β”‚
                                β–Ό
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚   Test Execution    β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                β”‚
                β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                β–Ό               β–Ό                 β–Ό
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚ HTML Report β”‚ β”‚Allure Reportβ”‚   β”‚   Artifacts β”‚
        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β”‚
                               β–Ό
                         β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                         β”‚Email Report β”‚
                         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ“‹ Framework Capabilities

Capability Status
Page Object Model βœ…
Playwright Test βœ…
Custom Fixtures βœ…
Environment Management βœ…
Environment-Aware Test Data βœ…
Excel Data-Driven Testing βœ…
Faker Test Data βœ…
Smart Click βœ…
Smart Fill βœ…
Smart Wait βœ…
Retry Utility βœ…
Assertion Utility βœ…
Soft Assertions βœ…
Execution Dashboard βœ…
Cross Browser Testing βœ…
Mobile Web Testing βœ…
HTML Reporting βœ…
Allure Reporting βœ…
Allure Environment βœ…
Allure History βœ…
Allure Trends βœ…
Screenshots βœ…
Videos βœ…
Playwright Traces βœ…
Email Reporting βœ…
Report ZIP Packaging βœ…
CI/CD Ready βœ…

πŸ“¦ Release History

πŸš€ v1.2.0 - Enterprise Reporting & Test Execution Update

Framework

  • Custom Playwright Fixtures
  • Environment-Aware Test Data Management
  • Improved Framework Architecture

Reporting

  • Allure Reporting
  • Allure Environment Information
  • Allure History
  • Allure Trends
  • Email Execution Reporting
  • Execution Summary
  • Automatic Report Packaging

Test Execution

  • Soft Assertion Support
  • Screenshots
  • Videos
  • Playwright Traces
  • Global Setup & Teardown Reporting Integration

Report Distribution

  • Allure Report ZIP
  • Playwright HTML Report ZIP
  • Email Attachments

πŸš€ v1.1.0 - Intelligent Execution Update

  • Environment Management
  • Execution Dashboard
  • Smart Retry Utility
  • Smart Click Utility
  • Smart Fill Utility
  • Smart Wait Utility
  • Assertion Utility

πŸš€ v1.0.0

  • Page Object Model
  • Excel Data Driven Framework
  • Cross Browser Testing
  • Mobile Browser Automation
  • API Utility
  • Database Utility
  • HTML Reporting
  • Organized Artifacts

πŸ›£οΈ Future Roadmap

Future versions may include:

  • πŸ€– AI-Assisted Test Generation
  • πŸ”Œ Playwright MCP Integration
  • πŸ€– AI Agent Support
  • 🧠 Intelligent Failure Analysis
  • 🩹 AI-Assisted Automation Recovery
  • πŸ”” Slack / Teams Notifications
  • 🐳 Docker Integration
  • ☁️ Cloud Browser Execution
  • πŸ“Š Advanced Execution Analytics

AI and self-healing capabilities are intentionally planned for a future AI-enabled evolution of the framework.


🀝 Contributions

Contributions are always welcome.

If you'd like to improve this framework:

  1. Fork the repository
  2. Create a feature branch
  3. Implement your changes
  4. Commit your changes
  5. Push the branch
  6. Submit a Pull Request

πŸ’Ό Services

Available for:

  • Playwright Framework Development
  • QA Automation
  • UI Automation
  • API Automation
  • Mobile Web Automation
  • Test Framework Design
  • Test Data Management
  • Reporting Framework Development
  • CI/CD Integration
  • Automation Consulting

πŸ’¬ Collaboration

Open to collaboration, knowledge sharing, and freelance opportunities around:

  • Playwright Automation
  • Test Automation Frameworks
  • QA Automation
  • JavaScript / Playwright
  • Test Data Management
  • Reporting Automation
  • CI/CD Automation

Feel free to connect and discuss automation requirements or framework development opportunities.


⭐ Support

If this project helped you:

⭐ Star this repository

🍴 Fork it

πŸ’‘ Suggest Improvements

🀝 Contribute

πŸ“’ Share it with other automation engineers


πŸ“„ License

This project is intended for:

  • Learning
  • Experimentation
  • Framework Development
  • Professional Automation Use

πŸš€ Made with ❀️ by Priyanshu Pathak

About

Production Ready Playwright Automation Framework

Resources

Stars

7 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages