---
id: TST-PFM-MTD-033
title: custom objects
kind: browser-lifecycle
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/custom-objects.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: 5
isolation: Fresh browser mock state and scenario-tagged records.
evidence:
  - 'react-console:e2e/mock/custom-objects.mock.spec.ts'
  - 'react-console:e2e/mock/custom-objects.mock.spec.ts#the list shows the active boats and opens one'
  - >-
    react-console:e2e/mock/custom-objects.mock.spec.ts#creating a boat requires Survey Due once Insured is
    ticked
  - >-
    react-console:e2e/mock/custom-objects.mock.spec.ts#a duplicate hull number is refused with the service's
    words
  - >-
    react-console:e2e/mock/custom-objects.mock.spec.ts#publishing, archiving and restoring a boat leave a
    history
  - 'react-console:e2e/mock/custom-objects.mock.spec.ts#a person who can only read is offered no action'
  - >-
    react-console:e2e/mock/custom-objects.mock.spec.ts#saving over a changed record offers a reload that keeps
    what was typed
fixture_imports:
  - '@playwright/test'
  - ../support/routes
test_doubles:
  - Mock API handlers and browser-local persona permissions.
limitations:
  - >-
    Browser assertions do not verify real server permission enforcement, database transactions or deployed
    delivery.
unmatched_specification: FND-PFM-MTD-083
binding_assertions: []
---

# Custom objects

## Verification Boundary

This browser suite checks custom record journeys within the console’s mock target. The registered file and pinned revision define its boundary.

## What This Suite Proves

The suite contains executable checks for this module, but no matching detailed scenario is established in this back-fill. The executable coverage finding records that mapping gap. Assertions are evidence of implemented checks; no execution result is claimed.

## What It Does Not Prove

The register does not establish a current passing run or full specification conformance. Browser assertions do not verify real server permission enforcement, database transactions or deployed delivery.

## Real Dependencies and Test Doubles

The console components and browser actions run against mock service responses. Mock API handlers and browser-local persona permissions.

## Must Not Be Doubled

A mock run must remain labeled as browser evidence. Real authorization, concurrency, commit-time history and storage cleanup require their own live or database-backed proof.