Skip to content

Scope, fee and working days are published on every engagement

support@corephysixlabs.com 7702752958 Track an order
CorePhysix Labs Technology lab
Start a project
01 / WEB Web & App Engineering 5 engagements · from ₹24,999 02 / CLD Cloud & DevOps 5 engagements · from ₹12,999 03 / DAT Data & AI 5 engagements · from ₹14,999 04 / UXD Product Design & UX 5 engagements · from ₹14,999 05 / API APIs & Integrations 5 engagements · from ₹18,999 06 / SEC Security & Compliance 5 engagements · from ₹12,999 07 / QAT QA & Test Automation 5 engagements · from ₹12,999 08 / SUP Managed Support 5 engagements · from ₹8,999 09 / ADV Tech Advisory 12 engagements · from ₹100

Not sure where to start?

Book a short advisory session and let a specialist point you to the right engagement.

See advisory sessions Full catalogue

Specification QAT·102

QAT · QA & Test Automation Defined scope Fixed fee

API Contract Test Pack

Contract tests that fail the build when an API response changes shape, so back-end releases stop breaking your apps and partners.

Fee · GST incl.
₹18,999
Duration
9 working days
Deliverables
7

01 Overview

An API that stays online can still break its clients, for instance when a field quietly starts returning null. Contract tests exist to catch exactly that. Our suite checks each response against its schema, verifies status codes and error formats, and enforces the authorisation rules that matter, such as a customer never being able to load someone else's record. Because it runs on every pull request, a breaking change surfaces as a red build instead of a partner's support ticket weeks after release.

02 Deliverables

7 items

What you receive at handover

  1. D01 Schema-validated contract tests for up to 40 endpoints
  2. D02 Assertions on status codes, error formats and headers for each endpoint
  3. D03 Authorisation tests for role boundaries and object-level access
  4. D04 Negative tests for malformed input and missing fields
  5. D05 CI integration that reports exactly which contract broke
  6. D06 Schema snapshots so unintended changes appear in a diff
  7. D07 Written guidance on adding tests as new endpoints are built

03 Outcomes

What should be true once it ships

  • Breaking changes fail in CI rather than on a customer's device
  • Refactoring becomes safer because the contract is checked automatically
  • App versions already installed keep working after server releases

04 Process

How the 4 stages run

  1. Baseline Endpoints are catalogued and their current response shapes recorded
  2. Specify Expected contracts are confirmed with your engineers and gaps flagged
  3. Build Tests are written for each endpoint, including negative and authorisation cases
  4. Integrate The suite joins CI and is demonstrated with a deliberate breaking change

05 Fit & inputs

A good fit for

  • Teams whose mobile app updates more slowly than the server
  • Products whose API is consumed by external partners
  • Back ends that nobody wants to refactor for fear of what might break

What we need from you

  • API access, with credentials for every role
  • An OpenAPI specification if one exists, though we can work without it
  • An engineer to confirm intended behaviour where it is unclear

These inputs are collected through the technical brief in your dashboard after payment. The duration is counted from when they arrive.

06 Answers

Questions about this engagement

Unit tests check internal logic. Contract tests check the promises your API makes to every client that consumes it.

We record current behaviour and confirm with you what is intentional. That step usually turns up a few surprises.

Yes, using schema and query-level assertions. The approach and the fee are the same.

This is technology work delivered digitally — nothing is shipped. Work is delivered into systems you control within the duration stated above, and the delivery and refund policies set out what happens if a date is missed.

REL Related

Often considered alongside.

All QA & Test Automation
QAT — QA & Test Automation QAT·101

Playwright End-to-End Test Suite

Playwright browser tests for your critical user journeys, running in CI and built to stay stable, so regressions stop reaching customers.

Playwright suite of around 40 scenarios covering your critical journeys

Fixed fee · GST incl.

₹34,999

Duration

20 working days

View scope
QAT — QA & Test Automation QAT·104

Load and Performance Test Run

k6 load testing that finds your breaking point and the component that fails first, so capacity problems are fixed before peak traffic.

Load model based on your real traffic patterns and expected peaks

Fixed fee · GST incl.

₹24,999

Duration

12 working days

View scope

GST included

₹18,999

Next step

Have a system that needs building, fixing or securing?

Explore the catalogue Describe the problem