Software Engineer at Total Shift Left
Smeet is a Software Engineer at Total Shift Left specialising in building scalable software systems with Flutter and Node.js. He has deep hands-on experience implementing API integrations that enable efficient data retrieval and utilisation within enterprise applications. At Total Shift Left, Smeet helps customers implement scalable API automation — from initial integration design through production-grade test pipelines — and writes about the practical engineering patterns that make API automation work at scale.
API mocking lets frontend, backend, and integration teams build against an API before it exists. Here is how dynamic mock servers unblock parallel development — and where mocking ends and contract testing begins.
Automate API testing in GitHub Actions with reusable workflows, quality gates, and PR status checks. Step-by-step guide from workflow YAML to production deployment gates.
Configure automated API testing in Azure DevOps pipelines with quality gates, JUnit reporting, and coverage tracking. Step-by-step guide from YAML pipeline setup to deployment gates.
Set up automated API testing in Jenkins pipelines with plugins, Jenkinsfile configuration, and quality gates. Complete guide from plugin installation to production-ready API quality enforcement.
How to measure, gate, and close gaps in OpenAPI test coverage in 2026. The four dimensions that matter, the AI-driven measurement pipeline, and the practical fixes for the five most common coverage gaps.
A vendor-level comparison of the best API test automation tools for backend teams — scored on CI/CD integration depth, spec-driven generation, authentication, coverage tracking, and total cost of ownership at 200+ services.
A practical guide to measuring API test coverage across endpoint, schema, scenario, and contract dimensions — with reporting patterns, thresholds, and CI/CD quality gates that block regressions before they ship.
Self-healing API tests automatically adapt when your API changes in non-breaking, spec-documented ways -- adding optional fields, extending enums, or adding new endpoints. By comparing test expectations against the current OpenAPI specification, they distinguish between intentional changes and actual regressions, eliminating the test maintenance tax that causes teams to abandon comprehensive test suites.
Understand the key differences between API penetration testing and API security testing, when to use each approach, and how to combine them for complete API protection.
