---
id: TST-PFM-MTD-074
title: placement apps
kind: unit
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/custom-objects/tests/unit/placement-apps.spec.ts
implements:
  - ATS-PFM-MTD-010-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - 'services-platform:modules/custom-objects/tests/unit/placement-apps.spec.ts'
  - >-
    services-platform:modules/custom-objects/tests/unit/placement-apps.spec.ts#are the console’s seventeen
    navigation apps, in its order
  - >-
    services-platform:modules/custom-objects/tests/unit/placement-apps.spec.ts#include orders, meetings and
    eligibility, which the licensing keys do not carry
  - >-
    services-platform:modules/custom-objects/tests/unit/placement-apps.spec.ts#leave out a licensing key the
    console has no app for, and anything that is not a string
fixture_imports:
  - chai
  - ../../../licensing/catalog/application-keys
  - ../../placement-apps
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-010-01
    provenance: test
    source:
      - >-
        services-platform:modules/custom-objects/tests/unit/placement-apps.spec.ts#are the console’s seventeen
        navigation apps, in its order
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Placement apps

## Verification Boundary

This unit suite checks custom objects and records within the local test harness. The registered file and pinned revision define its boundary.

## What This Suite Proves

The bindings identify the detailed or feature scenarios whose outcomes have assertions in this suite. Original case references remain attached to the detailed scenarios so a reviewer can inspect the exact assertion. Assertions are evidence of implemented checks; no execution result is claimed.

## What It Does Not Prove

The register does not establish a current passing run or full specification conformance. Behavior outside the suite’s fixtures and assertions remains unverified.

## Real Dependencies and Test Doubles

The imported contract and validation code runs locally. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The contract or validation function under examination must run directly; expected outputs cannot replace it.