---
id: TST-ACC-BAT-065
title: Batch integration batches view
kind: integration
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/batches/tests/integration/db/batches-view.integration.spec.js
implements:
  - ATS-ACC-BAT-002-10
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 its test workspace or fixed integration fixtures in the
  prepared local database.
assertion_sources:
  - scenario: ATS-ACC-BAT-002-10
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/db/batches-view.integration.spec.js#answers
      the reader of tenant A its batches, with every column, the number the code
      else the name
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/db/batches-view.integration.spec.js
    note: >-
      The executable file is inspected at the pinned revision; duration is an
      unmeasured planning estimate.
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/db/batches-view.integration.spec.js#suite
      header
    note: >-
      Real: PostgreSQL, the migrations, row-level security, the batches' and the
      configuration persistence. Doubled: nothing.
unbound_scope: >-
  The suite is registered as executable evidence but no existing scenario is
  claimed to execute completely in this file.
---

# Batch integration batches view

## Verification Boundary

This suite exercises the imported batch services or storage against the prepared local database. It does not imply that a deployed workflow is contacted.

## What This Suite Proves

Reporting exposes each workspace’s own collections and chooses the displayed number from code or name. The assertion anchors identify the supported portions of the bound scenarios.

## What It Does Not Prove

Local assertions do not establish deployment configuration, remote delivery guarantees, or unasserted lifecycle and concurrency paths.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised persistence or accounting functions are real. Controlled clocks, imported test fixtures and any suite-specific doubles delimit the asserted behavior.

## Must Not Be Doubled

The database constraints, transaction boundaries and exercised accounting functions must remain real when qualifying the asserted persistence or generation behavior.