---
id: TST-ACC-BKS-187
title: Schedules End To End integration suite
kind: integration
product_area: accounting
module: books
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-accounting
files:
  - >-
    modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js
implements:
  - ATS-ACC-BKS-010-03
  - ATS-ACC-BKS-010-05
  - ATS-ACC-BKS-018-05
  - ATS-ACC-BKS-018-09
  - FAS-ACC-BKS-03-02
  - FAS-ACC-BKS-06-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  The suite owns isolated workspace identities and database fixtures; cleanup
  removes only its seeded records.
assertion_bindings:
  - scenario: ATS-ACC-BKS-010-03
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#fails
      the roll dated in no fiscal year of the unit, with the sentence naming the
      date and the unit
  - scenario: ATS-ACC-BKS-010-03
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#records
      the fiscal year and period containing the batch date in the plan of the
      roll once the year exists
  - scenario: ATS-ACC-BKS-010-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#fails
      the roll dated in no fiscal year of the unit, with the sentence naming the
      date and the unit
  - scenario: ATS-ACC-BKS-018-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is
      claimed exactly once
  - scenario: ATS-ACC-BKS-018-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is
      never claimed
  - scenario: ATS-ACC-BKS-018-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#runs
      once, at 03:30 local (07:30 UTC), the first instant after the gap
  - scenario: ATS-ACC-BKS-018-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#dates
      the batch the 9th, the local date of the roll
  - scenario: ATS-ACC-BKS-018-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses
      the schedule after the fifth failure in a row
  - scenario: ATS-ACC-BKS-018-09
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#dates
      the batch the 9th, the local date of the roll
  - scenario: FAS-ACC-BKS-03-02
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#fails
      the roll dated in no fiscal year of the unit, with the sentence naming the
      date and the unit
  - scenario: FAS-ACC-BKS-06-05
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses
      the schedule after the fifth failure in a row
unmapped: false
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js
execution_notes: >-
  The file exists at the pinned revision; this registration records no execution
  result.
---

# Schedules End To End integration suite

## Verification Boundary

The suite exercises workspace operations against the migrated local database. Its fixtures and transaction contexts determine the records and service paths under test.

## What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

## What It Does Not Prove

Local database execution does not prove deployed infrastructure, external provider availability or console behavior. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

## Real Dependencies and Test Doubles

PostgreSQL, dispatcher, consumer, schedule repository and registered recurring work are real. A recording publisher stands for the queue, a manual clock fixes time, and the repeated-failure case doubles the period-lookup port.

## Must Not Be Doubled

The database constraints, transaction paths and production persistence functions named by the assertions must remain real. A memory store cannot establish the recorded database proof.