---
id: TST-ACC-BAT-051
title: Console reporting classic
kind: browser-lifecycle
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/reporting-classic.mock.spec.ts
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
isolation: Each browser context owns in-memory mock records.
assertion_sources: []
evidence:
  - provenance: observed
    source: 'react-console:e2e/mock/reporting-classic.mock.spec.ts'
    note: >-
      The executable file is inspected at the pinned revision; duration is an
      unmeasured planning estimate.
unbound_scope: >-
  The suite is registered as executable evidence but no existing scenario is
  claimed to execute completely in this file.
---

# Console reporting classic

## Verification Boundary

This browser suite exercises the console against simulated responses and state. It proves the asserted display and interaction behavior within that model.

## What This Suite Proves

Simulated ledger reports compare batch and grand totals, currency separation, filters and links with the sample lines. No complete scenario binding is claimed for these recorded assertions.

## What It Does Not Prove

Mock success does not establish database guards, account generation or deployed job completion. Mock accounting choices can differ from native outcomes.

## Real Dependencies and Test Doubles

The browser and rendered components are real; service replies, job outcomes and persistence are simulated by the mock application.

## Must Not Be Doubled

Future qualification of accounting integrity must use real persistence, generation and job execution. These browser doubles remain suitable for display and interaction checks.