---
id: TST-ACC-PRD-022
title: Product and financial editor with mocked services
kind: browser-lifecycle
product_area: accounting
module: products
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/accounting-products.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
estimation_note: Planning estimate; no runtime measurement is claimed.
isolation: A fresh browser context with its own seeded mock store.
evidence:
  - 'react-console:e2e/mock/accounting-products.mock.spec.ts'
assertion_bindings: []
coverage_note: >-
  This executable file has no complete current scenario binding; its existence does not establish acceptance
  coverage.
---

# Product and financial editor with mocked services

## Verification Boundary

The browser runs the built console against request handlers and page-local seeded data. It verifies presentation and client requests within the mocked contract.

## What This Suite Proves

The browser checks creation, pricing choices, recognition totals, donation presentation and conflict reload.

## What It Does Not Prove

Mocked responses do not establish backend rule enforcement, row locks, transactions or deployed permission behavior.

## Real Dependencies and Test Doubles

The console and browser are real. Network services, authorization answers and stored records are supplied by mock handlers.

## Must Not Be Doubled

Keep the browser interactions, client validation, request serialization and state transitions real. Backend persistence, permissions and transactions require separate real-service proof.