---
id: TST-PFM-MTD-088
title: custom object forms
kind: api-lifecycle
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js
implements:
  - ATS-PFM-MTD-008-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - 'services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js'
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#stores a form for the purpose
    of an active custom object
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#lets a reader of custom
    records read the form
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#lists the form for a reader of
    custom records
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#refuses a reader of custom
    records a change to the form, 403
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#refuses a caller who holds no
    custom objects key the form, 404
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#stores a form for a draft
    custom object, which is designed before it is active
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#refuses a form for a custom
    object the tenant does not have, 404
  - >-
    services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#answers 404 for a stored form
    once its custom object is archived
fixture_imports:
  - chai
  - ../../../../aws/api/platform-api-handler
  - '@rhythmsoftware/macroservice-testing/signed-context'
  - '@rhythmsoftware/macroservice-testing/stage'
  - '@rhythmsoftware/macroservice-execution/tenant-time-zones'
  - ../../../tenants/services/persistence/tenants
  - ../../aws/api/layouts.routes
  - ./route-callers
  - ../integration/support
  - ../../../custom-objects/tests/integration/support
  - ../../../custom-objects/services/persistence/custom-objects
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-008-06
    provenance: test
    source:
      - >-
        services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#lets a reader of custom
        records read the form
      - >-
        services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#refuses a reader of custom
        records a change to the form, 403
      - >-
        services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#refuses a form for a
        custom object the tenant does not have, 404
      - >-
        services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#answers 404 for a stored
        form once its custom object is archived
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Custom object forms

## Verification Boundary

This API suite checks reusable record presentations within the local test harness. The registered file and pinned revision define its boundary.

## What This Suite Proves

The bindings identify the detailed or feature scenarios whose outcomes have assertions in this suite. Original case references remain attached to the detailed scenarios so a reviewer can inspect the exact assertion. 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. Behavior outside the suite’s fixtures and assertions remains unverified.

## Real Dependencies and Test Doubles

The fixture uses PostgreSQL and the imported persistence or API code. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The operation under examination and its asserted stored outcomes must remain real within the declared harness. A fixture cannot replace the write, refusal or transactional effect that the bound scenario checks.