🎭 Cross-Browser E2E Automation Framework: Playwright, Python & Pytest

End-to-End Web Testing with Playwright (Python bindings) and Pytest

This repository is an automated end-to-end (E2E) testing suite built with Playwright for Python and pytest-playwright. It runs user journeys against the OWASP Juice Shop application across Chromium, Firefox and WebKit, using isolated browser contexts and a headless Docker runner.

It is the Playwright layer of a larger CI/CD ecosystem: docker-test-env runs it with Juice Shop inside a Jenkins pipeline, alongside the Cypress, Selenium and API suites.

---

🗺️ Quick Navigation

• Engineering Highlights
• Architecture
• Where It Fits: CI/CD Pipeline
• Tech Stack
• Project Structure
• Covered Scenarios
• Running Locally
• Running via Docker
• Roadmap

---

💡 Engineering Highlights

• Cross-Browser Execution: Runs the same tests on Chromium, Firefox and WebKit, reducing platform-specific surprises.
• Isolated Browser Contexts: Each test gets a fresh, independent browser context, so cookies, cache and session state do not leak between tests.
• Failure Diagnostics: Built on pytest-playwright, which supports screenshots and traces on failure to help root-cause analysis.
• Environment-Driven Configuration: The base URL is a parameter, so the same suite runs on a developer machine or inside containers.

---

🧭 Architecture

flowchart LR
    PT["Pytest<br/>conftest.py and tests"] --> PP["pytest-playwright<br/>Fixtures"]
    PP --> CTX["Isolated Browser Context<br/>per test"]
    CTX --> CH["Chromium"]
    CTX --> FF["Firefox"]
    CTX --> WK["WebKit"]
    CH --> JS["OWASP Juice Shop"]
    FF --> JS
    WK --> JS
    PT -.->|"on failure"| ART["Screenshots and Traces"]

Loading

---

🧭 Where It Fits: CI/CD Pipeline

flowchart LR
    JK["Jenkins Pipeline"] --> D["Docker Compose<br/>docker-test-env"]
    D --> JS["OWASP Juice Shop"]
    D --> PWC["Playwright Python Container<br/>mcr.microsoft.com/playwright/python<br/>this repository"]
    PWC -->|"Headless browsers"| JS
    PWC --> R["Test Results<br/>and Failure Artifacts"]
    R --> JK

Loading

---

🛠️ Tech Stack and Dependencies

• Automation Engine: Playwright 1.48+ (Python bindings)
• Test Runner: pytest with pytest-playwright
• Infrastructure: Official Microsoft Playwright container image for headless runs in Jenkins CI/CD (via docker-test-env)

---

📁 Project Structure

e2e-playwright-python/
├── requirements.txt
├── pytest.ini
└── tests/
    ├── conftest.py
    └── test_juice_shop_login.py

---

🔍 Covered Scenarios

• Home page: loads successfully and lists the product components.
• Navigation: the login page renders when opened from the account menu.
• Invalid login: an error message is displayed when invalid credentials are submitted.

---

🚀 Running Locally

Prerequisites: Python 3.10+ and a running instance of Juice Shop (locally or in a container).

Windows (PowerShell):

python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt
playwright install
pytest --base-url=http://localhost:3001 --browser chromium --browser firefox --browser webkit

Linux / macOS:

python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
playwright install --with-deps
pytest --base-url=http://localhost:3001 --browser chromium --browser firefox --browser webkit

---

🐳 Running via Docker (CI/CD Orchestration)

This repository is consumed by the docker-test-env orchestration project. The pipeline starts Juice Shop and runs this suite inside the official mcr.microsoft.com/playwright/python container image, triggered and tracked by a unified Jenkins pipeline. See that project's docker-compose.yml for the full setup.

---

🔗 Related Projects

• docker-test-env: Docker Compose + Jenkins + SonarQube orchestration
• e2e-cypress-js: Cypress E2E suite
• e2e-selenium-java: Selenium 4 + JUnit 5 suite
• api-testing: REST API tests with Pytest
• Profile & ecosystem overview

---

📈 Roadmap and Next Steps

• Integrate pytest-html to generate visual reports and archive them as CI artifacts
• Expand coverage to multi-step cart, basket and checkout flows
• Combine UI tests with API-level setup and checks (see api-testing)

---

⚖️ License

This repository is licensed under the MIT License. Feel free to clone, study, modify, and distribute the code for educational or portfolio purposes.

---

👤 Author

Alexsander Corvello da Silveira, Senior QA Engineer focused on AI-driven testing and applied machine learning. GitHub: @acorvello