---
id: TST-PFM-OPS-105
title: Workspace applications 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/tenant-applications.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/tenant-applications.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/tenant-applications.queries.integration.spec.js#answers
    one record per registered application, including the ones the tenant has nothing for
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#maps
    every element of a record: the key, both states, the verdict and the reason
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#answers
    a granted and enabled application as available, with no reason at all
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#answers
    a granted application that is still provisioning as unavailable, with that as the reason
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#answers
    a granted application whose provisioning failed with that reason, not the licence
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#answers
    a granted application that is suspended as unavailable
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#answers
    a granted application with no operational row as not_provisioned
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/tenant-applications.queries.integration.spec.js#reads
    an expired grant out of the decision, though the row is still in the table
---

# Workspace applications 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 workspace applications 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. The suite controls time where boundary checks require it.

## Must Not Be Doubled

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