I will write automated end to end tests using playwright and typescript
About this Gig
Are broken features or manual QA slowing your releases?
I build fast, reliable automated end-to-end (E2E) testing suites using Playwright & TypeScript. Stop wasting hours manually testing before every launchlet automated scripts verify your app in seconds.
Whether you run a Next.js SaaS, React web application, or complex API platform, I write clean, non-flaky Playwright tests to protect your revenue-critical workflows.
What I Offer:
E2E Automation: Auth, Stripe checkout, forms & dashboard CRUD workflows.
Cross-Browser Testing: Parallel execution across Chromium, WebKit (Safari) & Firefox.
Scalable Architecture: Clean Page Object Model (POM) design pattern.
Rich Reports: HTML execution logs with failure screenshots & video recordings.
CI/CD Pipeline: Auto-run tests via GitHub Actions or Vercel on every commit.
Tech Stack:
Playwright | TypeScript | Node.js | GitHub Actions | HTML Reports
Why Choose Me?
As a full-stack developer, I write tests from a code-first perspectiveensuring reliable selectors, smart auto-waiting, and zero test flakiness.
Select a package or message me for a custom automation strategy!
Testing application:
Website
Device:
PC
•
iPhone
•
iPad
•
Android mobile phone
•
Android tablet
FAQ
What do you need from me to get started?
I will need the URL of your staging or production application, test user credentials (if login is required), and a brief list of the core user actions/flows you want automated.
How do you handle authentication in Playwright tests?
I use Playwright's authenticated storage state session caching. This logs in once per test session and reuses the session state, making your test suite run significantly faster without burning API limits.
Can you integrate these automated tests into my GitHub repository?
Yes! In the Premium package (or via a custom add-on), I will set up a GitHub Actions workflow that automatically runs your Playwright test suite on every pull request or main branch merge.
What happens if my website's UI changes in the future?
I build test suites using the Page Object Model (POM) design pattern and resilient Playwright locators (like getByRole and getByTestId). If a UI element changes, you only need to update the selector in one central file rather than rewriting entire test scripts.
