---
id: TST-PFM-MTD-117
title: custom fields custom objects
kind: integration
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js
implements:
  - ATS-PFM-MTD-005-01
  - ATS-PFM-MTD-005-09
  - ATS-PFM-MTD-005-10
  - ATS-PFM-MTD-005-12
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/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#creates
    a property of an active custom object with a plain key
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#creates
    a property of a draft custom object, which is designed before it is active
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
    the __c suffix on a custom object, and creates nothing
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
    a key a custom object reserves for its fixed fields
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#still
    requires the __c suffix on a native object
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
    a property of a custom object the tenant does not have, as not found
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
    a property of an archived custom object, as not found
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#creates
    a reference property targeting another custom object
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
    a reference property targeting a custom object the tenant does not have
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#writes
    a field’s place and group, and reads them back
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#clears
    a field’s place and group when a replacement leaves them out
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#lists
    the properties of a custom object, the well-known Boat’s thirteen among them
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
    the 201st property, archived ones counted, and creates nothing
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#counts
    each object on its own, so a native object keeps its room
  - >-
    services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#does
    not cap a native object: contacts take a 201st custom field
fixture_imports:
  - drizzle-orm
  - '@rhythmsoftware/macroservice-errors/errors'
  - '@rhythmsoftware/macroservice-testing/refusals'
  - ../../../../db/custom-fields.table
  - ../../../../services/persistence/custom-fields
  - ../../../../../custom-objects/services/persistence/custom-objects
  - ../../../../../custom-objects/tests/integration/support
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-005-01
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
        the __c suffix on a custom object, and creates nothing
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
        a key a custom object reserves for its fixed fields
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#still
        requires the __c suffix on a native object
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
  - scenario: ATS-PFM-MTD-005-09
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
        the 201st property, archived ones counted, and creates nothing
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#counts
        each object on its own, so a native object keeps its room
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
  - scenario: ATS-PFM-MTD-005-10
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#refuses
        a property of an archived custom object, as not found
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
  - scenario: ATS-PFM-MTD-005-12
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/integration/services/persistence/custom-fields.custom-objects.integration.spec.js#clears
        a field’s place and group when a replacement leaves them out
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Custom fields custom objects

## Verification Boundary

This integration 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 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.