---
id: TST-PFM-NOT-067
title: lane bucket
kind: unit
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/communications/tests/unit/services/dispatch/lane-bucket.spec.js
implements:
  - ATS-PFM-NOT-018-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: Per-process test inputs and installed doubles.
assertion_bindings:
  - scenario: ATS-PFM-NOT-018-09
    suite: TST-PFM-NOT-067
    assertions:
      - >-
        services-platform:modules/communications/tests/unit/services/dispatch/lane-bucket.spec.js#lets
        the marketing lane take its 60 % and no more in one second
      - >-
        services-platform:modules/communications/tests/unit/services/dispatch/lane-bucket.spec.js#lets
        the transactional lane borrow the marketing lane’s unused tokens once
        its own are gone
      - >-
        services-platform:modules/communications/tests/unit/services/dispatch/lane-bucket.spec.js#never
        lets the marketing lane borrow the transactional lane’s reserved tokens
      - >-
        services-platform:modules/communications/tests/unit/services/dispatch/lane-bucket.spec.js#is
        not limited at all
evidence:
  - >-
    services-platform:modules/communications/tests/unit/services/dispatch/lane-bucket.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: `takeFromLanes` and `refill`. Doubled: nothing — these functions reach
    nothing. Never doubled: the rules under test.
---

# lane bucket

## Verification Boundary

This suite checks isolated calculations, validation or presentation with process-local inputs. It does not establish a deployed workflow.

## What This Suite Proves

Its cases exercise reserve lane capacity with one-way borrowing.

The registered scenario bindings identify the assertions this executable file contributes. They retain individual test references so that a composite scenario does not become a claim of complete execution by one file.

## What It Does Not Prove

Local outcomes do not prove deployed queues, external provider acceptance, production credentials or complete browser behavior. No fresh execution or conformance result is claimed.

## Real Dependencies and Test Doubles

The test file identifies its pure inputs or presentation doubles. Console component suites use recorded request handlers; pure validation suites require no external provider.

## Must Not Be Doubled

The calculation, validator or component under test must execute its real implementation. Doubles supply inputs and external responses without replacing the behavior being proved.