---
id: TST-PFM-MTD-085
title: upload presign
kind: unit
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/files/tests/unit/upload-presign.spec.ts
implements:
  - ATS-PFM-MTD-007-06
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/files/tests/unit/upload-presign.spec.ts'
  - >-
    services-platform:modules/files/tests/unit/upload-presign.spec.ts#names the bucket, the staging key and a
    15-minute lifetime
  - >-
    services-platform:modules/files/tests/unit/upload-presign.spec.ts#signs the type, the length and both
    metadata headers, so S3 refuses a PUT that changes any
  - >-
    services-platform:modules/files/tests/unit/upload-presign.spec.ts#leaves the metadata out of the query
    string, so the client must send it as headers
  - >-
    services-platform:modules/files/tests/unit/upload-presign.spec.ts#answers the headers the client sends
    with the PUT, exactly
fixture_imports:
  - chai
  - ../../services/uploads/upload-storage
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-007-06
    provenance: test
    source:
      - >-
        services-platform:modules/files/tests/unit/upload-presign.spec.ts#names the bucket, the staging key
        and a 15-minute lifetime
      - >-
        services-platform:modules/files/tests/unit/upload-presign.spec.ts#signs the type, the length and both
        metadata headers, so S3 refuses a PUT that changes any
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Upload presign

## Verification Boundary

This unit suite checks upload issuance 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.