---
id: TST-COM-FUL-029
title: Position view gate
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/fulfillment/tests/integration/services/facts/position-view-gate.integration.spec.js
implements:
  - ATS-COM-FUL-002-03
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: modules/fulfillment/tests/integration/services/facts/position-view-gate.integration.spec.js
    test_titles:
      - answers the card line’s pending capture and the invoice’s pro forma flag from the view
      - 'answers the ACH line’s pending amount from the view, not a pro forma'
      - sums a two-invoice line’s pending amounts and answers the newer change
      - closes paid_in_full on pending capture although the line is paid in full
      - >-
        closes paid_in_full on ACH pending when the policy waits for settlement, subtracting it from
        the paid money
      - opens paid_in_full on the same ACH line when the policy counts ACH once accepted
      - 'opens paid_in_full on a settled line, nothing pending'
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/facts/position-view-gate.integration.spec.js#closes
        paid_in_full on ACH pending when the policy waits for settlement, subtracting it from the
        paid money
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/facts/position-view-gate.integration.spec.js#opens
        paid_in_full on the same ACH line when the policy counts ACH once accepted
---

# Position view gate

## Verification Boundary

This suite checks position view gate against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.