---
id: TST-PFM-INT-478
title: resolution
kind: unit
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - modules/extensions/tests/unit/resolution.spec.js
implements:
  - ATS-PFM-INT-017-09
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Pure test fixtures owned by the test process.
evidence:
  - 'services-platform:modules/extensions/tests/unit/resolution.spec.js'
test_cases:
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#lets a product binding beat a
      tenant binding
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#falls back to the tenant binding
      when no more specific one matches the scope
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#prefers the more specific of two
      non-tenant scopes
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#lets the lowest priority win
      among equally specific matches
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#answers a tie as a configuration
      error naming both bindings
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#answers the default when no
      enabled binding matches
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#excludes a shadow binding from
      the selection and answers it beside the winner
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#answers matching shadow bindings
      even when only the default runs
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#never selects a draft, disabled
      or orphaned binding
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#runs every enabled match, most
      specific first, then by priority, then by id
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#leaves shadow bindings out of
      the run and answers them apart
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#never answers a tie: equal
      bindings both run
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#matches the tenant scope always,
      and another scope only by its id
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#never matches a scope kind the
      point does not declare
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#bounds a match by its half-open
      effective window
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#leaves a binding outside its
      window out of the resolution
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/unit/resolution.spec.js#ranks specificity by the scope
      kind’s position, the tenant last
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/extensions/tests/unit/resolution.spec.js'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# resolution

## Verification Boundary

This unit suite exercises resolution. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

## What It Does Not Prove

Pure cases do not establish database constraints, deployed authorization or provider effects.

## Real Dependencies and Test Doubles

The suite evaluates its imported functions with controlled inputs. Its source records the fixture and substitution boundary.

## Must Not Be Doubled

The function under test and its result checks must execute. Replacing them with expected answers provides no proof.