Home / Playwright test automation
Web test automation with Playwright and TypeScript
I design, automate and maintain Playwright/TypeScript tests for your web applications: user journeys, business rules and data. Freelance, working directly with you, remotely or on-site.
The problemWhat QA teams run into
- Manual acceptance testing that has to be redone in full on every release, with things missed.
- Automated tests that fail at random, until the team stops trusting them.
- Inconsistent reference data, caught too late.
- Test execution reports that are hard to compare from one run to the next.
- Tests that business teams can't read when they sign off on UAT.
ServicesWhat I take on
Building a test suite
Technical foundation (structure, helpers, selectors), then automated scenarios screen by screen.
Taking over an existing suite
Suite audit, stabilization of flaky tests, prioritization of the scenarios to fix.
Migrating from manual to automated UAT
Your manual test cases migrated to automated Playwright acceptance tests, entity by entity.
UAT aligned with the tests
UAT documentation business users can read, matching what the automated tests check.
ScopeTypes of tests covered
- End-to-end user journeys: search, open a record, create, edit, verify.
- Data checks: field validity and consistency across linked entities.
- Business rules: expected behavior according to the application's business rules.
- Test data management: data restored to its original state after each scenario, selection by unique identifier rather than by label.
- Run tracking: durations, passes and failures, run after run.
ProcessHow an engagement runs
- Initial discussion: your application, objectives, existing tests and constraints.
- Scoping: scope, priorities, expected deliverables and working arrangements.
- Delivery: the agreed work, with progress reporting defined at the start.
- Handover: deliverables and documentation, with a walkthrough for your team.
DeliverablesWhat you get
- The automated test scenarios (Playwright/TypeScript code).
- An organized, maintainable suite: structure, conventions, shared helpers.
- Test execution reports.
- Handover documentation for your team.
- Optional: UAT documentation and a run-tracking dashboard.
ExampleA case study: 1,300 manual tests migrated to automation
On a reference-data management application for an agribusiness group, I migrated the manual UAT (1,300 data validity and consistency tests) to automated acceptance testing, with user journeys, UAT documentation and a run-tracking tool.
FAQFrequently asked questions
Can you take over an existing Playwright test suite?
Yes. A takeover starts with an audit of the suite: flaky tests, fragile selectors, test data. I then stabilize the scenarios in order of priority.
Can you write UAT test cases before automation?
Yes. I write the test cases from your specifications or business rules, then automate the ones that lend themselves to it.
How do you estimate effort?
From the scope: number of scenarios, business rules, test data and the current state of the application. The online estimator gives a first order of magnitude; the final quote follows a scoping call.
A Playwright automation project?
Describe your application and your goals. I'll reply by email within two business days.