Build
01New Unit and integration work from requirement to production: test suites added to legacy projects before a big change; Feature tests for APIs, forms and permissions; Test setup, factories and CI for teams starting out.
QA and testing · 5 technologies
Unit and integration — tests developers run before they push.
Unit and integration tests are what let a codebase change without fear. I add them to projects that have none, starting with the parts that matter, and I keep them fast so they run before every push rather than once a quarter.
- Technologies
- PHPUnit · Pest · Jest · Vitest · PyTest
- Support
- Build · fix and maintain · upgrade and migrate · audit and advise
- Typical
- Test suites added to legacy projects before a big change
- Pricing
- Fixed price, or hourly from $10 by stack
- Team
- Me, plus a vetted team of 50+ for larger builds, 90% with 10+ years' experience
- Start
- Usually within one working day of agreeing the scope
01 — What I do with Unit and integration
build, fix, upgrade, audit
Fix and maintain
02The usual problems in existing Unit and integration systems: zero tests, a fear of touching anything, and bugs returning after they were fixed.
Upgrade and migrate
03PHPUnit to Pest where teams prefer it, Jest to Vitest with Vite, slow database tests to fast ones.
Audit and advise
04A code, security, performance and SEO audit of your Unit and integration system, with a written plan you can act on with or without me.
02 — Technologies
what each one is for
PHPUnit
The standard for Laravel and PHP.
Pest
Expressive PHP tests on top of PHPUnit.
Jest
JavaScript and React testing.
Vitest
Fast tests for Vite-based projects.
PyTest
Python testing with fixtures and plugins.
03 — Typical projects
what people usually ask for
Unit and integration work
that actually gets ordered.
Three shapes most Unit and integration engagements take. Yours may be a fourth; describe it and I will tell you honestly whether it fits.
- Test suites added to legacy projects before a big change
- Feature tests for APIs, forms and permissions
- Test setup, factories and CI for teams starting out
04 — Questions
about Unit and integration work
Our project has no tests. Where do we start?
With the flows that cost money when they break: login, payment, orders. A dozen feature tests there change how safely the team can work.
Do tests slow development down?
They slow the first week and speed up every week after. The alternative is testing by hand, forever.
How is Unit and integration work priced?
A fixed price for a defined scope, or hourly from $10 depending on the stack, always with a written estimate before any work starts.
How do we start?
Send a short description of what exists and what you need. You get a reply within one working day with questions, then a scope or an estimate.
06 — Start
describe the Unit and integration project
Got a Unit and integration project?
Tell me what exists, what you need, and the deadline if there is one. I reply within one working day with questions, then a scope or an estimate.
Ahmedabad, India · IST (UTC+5:30) · --:-- IST · Mon–Fri 09:00–18:00 IST · US & EU overlap daily