I will add automated tests with vitest jest playwright
Senior Full Stack React js Node js Three js React Native
About this Gig
Shipping features without tests? Afraid to refactor because something might break?
I add meaningful, maintainable automated tests to your React codebase
unit tests, integration tests, and component tests that actually catch real bugs.
I write tests with:
Vitest or Jest fast, modern test runners
React Testing Library testing behavior, not implementation
MSW (Mock Service Worker) realistic API mocking
user-event simulating real user interactions
Playwright or Cypress E2E tests for critical flows
What I test:
React components (render, interaction, conditional UI)
Custom hooks (state logic, side effects, async behavior)
Utility functions and business logic
API integration layers (with proper mocking)
Authentication and permission guards
Form validation flows
My tests follow the Testing Trophy model: maximum value per test written.
I don't write tests for coverage percentages I write tests that prevent real regressions
Testing application:
Web application
Device:
PC
•
Linux
•
iPhone
•
Android mobile phone
My Portfolio
FAQ
I have no tests at all. Where do you start?
With a brief audit of your codebase to identify the highest-risk, highest-value areas. Then I write tests there first.
Will tests slow down my CI pipeline?
Properly configured Vitest/Jest runs are fast. I'll also set up parallel test execution if needed.
Do you write E2E tests?
That's the add-on. For most codebases, I recommend starting with unit + integration, then adding E2E for critical flows only.
What if my code isn't testable?
Some codebases need light refactoring to be testable (extracting logic from components, etc.). I'll flag this upfront — minor refactors are included in the Advanced tier.
