---
id: TST-PFM-OPS-082
title: Applications table
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/licensing/tests/integration/db/applications.table.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/db/applications.table.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/db/applications.table.integration.spec.js#stores
    a declared licensing mode written directly, the negative control for the check below
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#refuses
    a licensing mode outside the closed list by applications_licensing_check
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#refuses
    a sys_locked value outside the closed list by applications_sys_locked_check
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#refuses
    a second row with the same id by the applications_pk primary key, so a key names one application
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#refuses
    a row with no name, naming the column
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#refuses
    a row with no display order, naming the column: the launcher’s only ordering instruction
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#refuses
    a row with no creator, naming the column
  - >-
    services-platform:modules/licensing/tests/integration/db/applications.table.integration.spec.js#admits
    an application with no description, the one fact of a registry row that may be absent
---

# Applications table

## 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 applications table 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.