How lambdatest/playwright-sample works
Main components
• Developer / CI Environment
– Local machine or GitHub Actions runner (defined in .github/workflows/tests.yml)
– Gitpod workspace (optional dev environment)
• Test Runners & Scripts
– JavaScript/TypeScript (playwright-test-js, playwright-test-ts, playwright-single.js, playwright-parallel.js, etc.)
– CodeceptJS (playwright-codecept-js)
– Cucumber.js (playwright-cucumber-js)
– .NET SpecFlow + xUnit (playwright-csharp-specflow-xunit)
– Plain C# (playwright-csharp)
– Java + JUnit (playwright-java-junit)
– Python samples (playwright-python)
– Jest integration (playwright-jest-js)
• Configuration & Credentials
– Environment variables (LT_USERNAME, LT_ACCESS_KEY)
– Framework config files (playwright.config.js/ts, codecept.conf.js, specflow hooks, pom.xml, package.json)
• LambdaTest Cloud
– Remote browser/device grid (3000+ environments)
– Authentication API (receives credentials over HTTPS)
– Test execution service (spawns browser sessions)
– Dashboard & persistence (stores logs, videos, test metadata)
• External Services
– GitHub (source code, workflows)
– Gitpod (optional)
Relationships & data flows
• Developer/CI → Test Runner: invokes npm/dotnet test/mvn test/pytest commands
• Test Runner → LambdaTest Cloud API: establishes WebSocket/REST connection with credentials
• LambdaTest Cloud → Remote Browsers: allocates and runs Playwright sessions on real browsers/devices
• Browser Sessions → LambdaTest Dashboard: streams video, logs, and results back to the cloud
• Developer/CI ← LambdaTest Dashboard: test results fetched via UI or API for reporting
Architectural patterns & principles
• Modular multi-language samples: each folder is an independent “adapter” for a language/framework
• Externalized configuration: all credentials and capabilities injected via env vars or config files
• CI integration: GitHub Actions orchestrates automated end-to-end tests on each push
• Service-oriented testing: decoupling test scripts from execution environment (Playwright → LT Cloud)
Essential details to capture
• Authentication handshake using LT_USERNAME / LT_ACCESS_KEY
• Playwright commands crossing network boundary into LT Cloud
• Session lifecycle: allocation → execution → reporting
• Storage of artifacts (screenshots, videos, logs)