---
id: TST-PFM-OPS-098
title: Hubspot contracts
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: >-
  The prepared local test database and suite-owned identifiers; existing hooks control rollback or
  cleanup.
evidence:
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js
    at ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: This existing engineering suite is registered without claiming a complete specification scenario.
assertion_sources:
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#writes
    every contract and every line the read answered
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#keeps
    the status, the term and the renewal flag exactly as HubSpot gave them
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#stamps
    the read it was last seen by, from the execution context\u2019s clock
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#writes
    nothing at all for a company HubSpot answered no contracts for, which is a customer who has bought
    nothing
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#ignores
    a line whose contract the read did not answer, which would otherwise be an orphan
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#leaves
    the same contracts and lines in place, changing nothing a reader sees but when they were seen
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#writes
    the new term when a contract is renewed in place
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-contracts.integration.spec.js#deletes
    a contract HubSpot no longer answers, and its lines with it
---

# Hubspot contracts

## Verification Boundary

This suite exercises application licensing through production operations against the local database. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks exercise hubspot contracts within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. No complete specification scenario is attributed to this suite yet.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database and production operations under test are real. Commercial-provider responses use the suite’s scripted inputs where declared. The suite controls time where boundary checks require it.

## Must Not Be Doubled

The persistence operations, database constraints and reads under assertion remain real.