---
id: TST-PFM-MTD-129
title: custom object properties
kind: unit
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/metadata/tests/unit/custom-object-properties.spec.ts
implements:
  - ATS-PFM-MTD-006-02
  - ATS-PFM-MTD-006-04
  - ATS-PFM-MTD-006-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - 'services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts'
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#accepts a plain snake_case
    key on a custom object
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses the __c suffix on a
    custom object, whose keys are plain
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a key a custom
    object reserves for its fixed fields
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#accepts the __c suffix on a
    registered object
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a plain key on a
    registered object, whose custom fields keep the suffix
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#accepts a length required
    when the status is restored
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#accepts a public exposure
    and a literal default the field can hold
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a condition naming
    a field the object does not have
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a field required
    because of itself
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a default the field
    cannot hold
  - >-
    services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses an exposure off the
    ladder before the description is read
fixture_imports:
  - chai
  - '@rhythmsoftware/macroservice-metadata/field-types'
  - '@rhythmsoftware/macroservice-metadata/field-definition'
  - '@rhythmsoftware/macroservice-metadata/field-rules'
  - '@rhythmsoftware/macroservice-metadata/object-description'
  - ../../../custom-objects/standard-fields
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-006-02
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a field
        required because of itself
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
  - scenario: ATS-PFM-MTD-006-04
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#accepts a public
        exposure and a literal default the field can hold
      - >-
        services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses a default the
        field cannot hold
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
  - scenario: ATS-PFM-MTD-006-05
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/unit/custom-object-properties.spec.ts#refuses an exposure off
        the ladder before the description is read
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Custom object properties

## Verification Boundary

This unit suite checks record descriptions and field configuration 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 imported contract and validation code runs locally. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The contract or validation function under examination must run directly; expected outputs cannot replace it.