Automated tests and code quality practices for reliable applications
Unit Testing
Isolated unit tests for business logic, services, and utility functions using JUnit (Java) and PHPUnit (PHP).
- JUnit 5 for Spring Boot
- PHPUnit for Laravel
- Test-driven development (TDD)
- Mocking & stubbing
End-to-End Testing
Browser-level automated tests with Selenium to verify user flows and catch regressions across the full application.
- Selenium WebDriver setup
- Page Object Model pattern
- Cross-browser test runs
- CI integration for e2e tests
Performance Optimisation
Profiling slow queries, reducing page load times, and applying caching strategies to improve application speed.
- Database query profiling
- Front-end bundle analysis
- Redis / cache implementation
- Core Web Vitals improvement
Code Quality
Consistent code standards, linting, and review practices to keep the codebase clean and maintainable.
- ESLint / Prettier (JS/TS)
- PHP CS Fixer (Laravel)
- Code review participation
- Refactoring & technical debt reduction
FAQ
Frequently Asked Questions
Yes — unit tests and integration tests are part of my standard workflow, especially for back-end services and APIs.
Yes — I can audit the codebase, identify high-risk areas, and incrementally add test coverage.
Yes — Selenium is part of my formal training and I have applied it in project QA workflows.
Yes — during my internship I actively participated in sprint planning, code reviews, and retrospectives following Scrum methodology.
I start by profiling (slow query log, browser DevTools, Lighthouse) to find the bottleneck, then apply the targeted fix — indexing, caching, lazy loading, etc.
Related services