---
id: TST-PFM-OPS-096
title: Hubspot company syncs
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-company-syncs.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-company-syncs.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-company-syncs.integration.spec.js#records
    the attempt, the success and how many contracts were seen
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#records
    a company HubSpot answered no contracts for, which is a read that worked and found nothing
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#clears
    the error the previous failure left
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#keeps
    one row per company however many reads there have been
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#records
    the attempt, the outcome and a reason
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#leaves
    the last success where it was, so that how long a company has been failing can still be read
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#records
    a reason even for a failure that gave none
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/hubspot-company-syncs.integration.spec.js#never
    records a query string, which is where a token could be
---

# Hubspot company syncs

## 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 company syncs 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.