Playwright Automated Testing Setup
Budget: ₹750 – ₹1,250 INR
I have a web application that now needs a solid, maintainable Playwright test suite. Before any scripts are written, I’d like you to review the current repo, identify gaps in testability, and outline a practical structure for end-to-end automated testing.
My immediate requirement is reliable coverage on Chrome; once that is in place we can consider extending the same suite to Firefox or Safari, but those are not in scope for this first milestone.
Here’s what I need from you:
• Project analysis: walk through the codebase, flag any blockers or quick wins that will influence Playwright implementation.
• Environment setup: configure Playwright, TypeScript (if you prefer), test runner, and reporting so that a new developer can clone, install, and run npm test without friction.
• Sample tests: write a handful of clear, well-commented scenarios that demonstrate login, a critical user flow, and basic assertions. These will serve as the template for our team.
• CI integration: wire the suite into our existing GitHub Actions workflow so tests run on every push and on pull-request.
Acceptance criteria
– `npm install && npm test` runs green locally in Chrome.
– Headed and headless modes are switchable via config.
– CI job passes with artifacts (screenshots/video) attached when tests fail.
– README section documents how to add new tests and switch browsers later.
If this aligns with your expertise, let me know your proposed approach and timeline, and we can get started right away.
My immediate requirement is reliable coverage on Chrome; once that is in place we can consider extending the same suite to Firefox or Safari, but those are not in scope for this first milestone.
Here’s what I need from you:
• Project analysis: walk through the codebase, flag any blockers or quick wins that will influence Playwright implementation.
• Environment setup: configure Playwright, TypeScript (if you prefer), test runner, and reporting so that a new developer can clone, install, and run npm test without friction.
• Sample tests: write a handful of clear, well-commented scenarios that demonstrate login, a critical user flow, and basic assertions. These will serve as the template for our team.
• CI integration: wire the suite into our existing GitHub Actions workflow so tests run on every push and on pull-request.
Acceptance criteria
– `npm install && npm test` runs green locally in Chrome.
– Headed and headless modes are switchable via config.
– CI job passes with artifacts (screenshots/video) attached when tests fail.
– README section documents how to add new tests and switch browsers later.
If this aligns with your expertise, let me know your proposed approach and timeline, and we can get started right away.