Part 3 - Playwright Interview Questions - CI/CD, GitHub Actions, Sharding, Docker, Azure

Most Playwright CI/CD tutorials give you disconnected question-and-answer clips. This video walks through it as one continuous story — every answer leads directly into the next problem, the same way a real interview conversation builds. We start from the most basic pain point — a test suite that's gotten too slow — and follow the chain all the way to a production-ready pipeline that combines GitHub Actions sharding with Docker. 🔹 What you'll learn: - What CI/CD actually means and why automated tests are the gatekeeper - How to structure a GitHub Actions workflow for Playwright - Where Playwright tests physically run, and why a single runner hits a wall - Two ways to scale: Azure cloud-hosted browsers vs GitHub Actions shards - How sharding actually works — shardIndex, shardTotal, and the --shard=X/N flag explained with a real example - Where Playwright workers fit in alongside shards, and how they multiply together - How to merge multiple shard reports into a single HTML report - Azure vs GitHub shards — real cost, scaling, and control trade-offs - The exact real-world failure GitHub's ubuntu-latest update caused for Playwright pipelines - What Docker is, and how it fixes that failure for good - The final, complete GitHub Actions YAML: sharding + Docker + merged reporting 📚 This video is part of Rahul Shetty Academy's Playwright Automation Testing Interview Series. 🔔 Subscribe to Rahul Shetty Academy for more QA automation content — Playwright, Selenium, API Testing, AI in QA, and career guidance for automation testers. 📚 Explore more: 🌐 Courses: https://rahulshettyacademy.com 🎯 QA Career Accelerator (Job Ready Program) https://rahulshettyacademy.com/qa-career-accelerator-job-ready #Playwright #PlaywrightInterviewQuestions #QAAutomation #SoftwareTesting #JavaScript #TypeScript #SDET #AutomationTesting #InterviewPreparation #RahulShettyAcademy