Refactor Playwright Automation Framework
Budget: €30 – €250 EUR
I’m handing over a sizeable Playwright + TypeScript code-base that already drives UI tests for several applications, but it has grown organically and is now tangled and hard to extend. The task is to turn this into a clean, abstracted platform that multiple product teams can plug into with minimal duplication.
Key refactor goals
• Break the current monolith into well-named, reusable modules, applying SOLID principles and proven design patterns so each layer knows exactly what it owns.
• Lift common logic into a shared core while keeping app-specific code thin and readable.
• Improve runtime performance by removing redundant waits, slimming fixture set-ups, and taking full advantage of Playwright’s parallel execution.
• Bake in a configurable reporting tool (I’m open to what you prefer) so every run outputs clear, actionable results in CI and locally.
I value clean code above quick hacks, so every pull request should reflect Clean Code guidelines and come with concise commit messages. If you can demonstrate the improvement—lowered execution time, reduced duplication, higher maintainability rating—I’ll consider the milestone complete.
You will work directly in my GitHub repo, raise PRs for review, and leave behind thorough README and inline docs so future engineers can evolve the framework without guesswork.
Key refactor goals
• Break the current monolith into well-named, reusable modules, applying SOLID principles and proven design patterns so each layer knows exactly what it owns.
• Lift common logic into a shared core while keeping app-specific code thin and readable.
• Improve runtime performance by removing redundant waits, slimming fixture set-ups, and taking full advantage of Playwright’s parallel execution.
• Bake in a configurable reporting tool (I’m open to what you prefer) so every run outputs clear, actionable results in CI and locally.
I value clean code above quick hacks, so every pull request should reflect Clean Code guidelines and come with concise commit messages. If you can demonstrate the improvement—lowered execution time, reduced duplication, higher maintainability rating—I’ll consider the milestone complete.
You will work directly in my GitHub repo, raise PRs for review, and leave behind thorough README and inline docs so future engineers can evolve the framework without guesswork.