---
id: TST-ACC-PRD-018
title: Shared product editor walk
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/dev/products-common-walk.dev.spec.ts
implements: []
environment: deployed-dev
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: Run-named records and owned business units in the development workspace; cleanup removes only run fixtures.
evidence:
  - 'react-console:e2e/dev/products-common-walk.dev.spec.ts'
assertion_bindings: []
coverage_note: >-
  This executable file has no complete current scenario binding; its existence does not establish acceptance
  coverage.
---

# Shared product editor walk

## Verification Boundary

The browser and API clients use the deployed development console and services with run-owned records. Skipped fixture steps do not count as executed behavior.

## What This Suite Proves

The walk exercises the shared editor and saved selling settings against development services; historical section expectations can differ from the pinned editor.

## What It Does Not Prove

A successful run covers only asserted steps; skipped database work and recorded observations do not establish domain rollback, complete export delivery or remote compensation.

## Real Dependencies and Test Doubles

The console, signed personas and development APIs are real dependencies. The run supplies its own unit, chart and records; unavailable infrastructure can skip a walk.

## Must Not Be Doubled

Do not replace authentication, service responses, persistence, posting or workspace isolation with browser stubs when claiming a deployed lifecycle result.