---
id: TST-PFM-OPS-102
title: Licence windows queries
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/licence-windows.queries.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/licence-windows.queries.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/licence-windows.queries.integration.spec.js#answers
    each window with every element of the record mapped
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#orders
    them by application, then by the day the licence starts
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#answers
    nothing for a company nobody has resolved windows for
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#answers
    the application and the three dates of each window, which is all the rule needs
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#answers
    an empty list for a company with no windows, which is a customer who has bought nothing
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#answers
    an empty list for a tenant with no HubSpot company, without a statement
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#answers
    a window on a day inside its term
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-windows.queries.integration.spec.js#answers
    a window on the last day of its term
---

# Licence windows queries

## 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 licence windows queries 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.

## Must Not Be Doubled

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