---
id: TST-COM-ORD-070
title: The download grant of a digital listing
kind: unit
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/entitlements/tests/unit/register/download-grant.spec.js
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The suite owns its in-memory inputs, scripted responses and rendered component state.'
evidence:
  - provenance: test
    source: 'services-commerce:modules/entitlements/tests/unit/register/download-grant.spec.js'
    test_cases:
      - carries the listing’s limit and window as they are within the bounds
      - 'is unlimited and windowless for a product with no listing, or a listing stating neither'
      - keeps a window of exactly the longest a grant runs
      - 'holds a window of 4000 days at the longest a grant runs, 3660'
      - holds a limit beyond the most uses a grant carries at that most
      - 'writes a payload that parses from a listing saved beyond both bounds, never throwing'
scenario_coverage: []
dependency_evidence:
  provenance: test
  source: 'services-commerce:modules/entitlements/tests/unit/register/download-grant.spec.js'
  declared_by_test: 'the function and the schema. Doubled: the listing, a literal record.'
---

# The download grant of a digital listing

## Verification Boundary

The unit suite checks the named contract or helper with controlled inputs.

## What This Suite Proves

The registered cases check the download grant of a digital listing with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

## What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

## Real Dependencies and Test Doubles

Inputs and external responses are controlled in process; this suite establishes no deployed service behavior.

## Must Not Be Doubled

The named contract validation or component behavior under assertion must use its actual implementation.