---
id: TST-PFM-MTD-115
title: describe custom object
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/describe/describe-custom-object.integration.spec.js
implements:
  - ATS-PFM-MTD-002-03
  - ATS-PFM-MTD-002-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/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#names
    the object as custom, with the labels of the tenant’s row
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#lists
    the fixed standard fields, the publication pair among them, then the thirteen properties in display order
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#describes
    the fixed fields as standard, with where a client may write each
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#points
    the two who-columns at Users, as every description does
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#gives
    every property its group, its place and its rules, exposure staff where it stores none
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#describes
    a property as a custom field of its data type, writable, required as the tenant set it
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#names
    a reference property’s target custom object with its labels
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#answers
    no collections
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#describes
    a draft, without the publication pair it is not publishable for
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#refuses
    an archived object as not found
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#refuses
    an object the tenant does not have as not found
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#refuses
    another tenant’s object as not found
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#refuses
    a system description of a custom object, which belongs to a tenant
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#describes
    it with its group, its place and its rules
  - >-
    services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#leaves
    the object registered, its identity carrying no custom origin
fixture_imports:
  - '@rhythmsoftware/macroservice-errors/errors'
  - '@rhythmsoftware/macroservice-testing/refusals'
  - '@rhythmsoftware/macroservice-testing/stage'
  - ../../../../services/describe/describe-object
  - ../../../../services/persistence/custom-fields
  - ../../../../../custom-objects/services/persistence/custom-objects
  - ../../../../../custom-objects/tests/integration/support
  - ../../../../db/custom-fields.table
  - drizzle-orm
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-002-03
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#refuses
        an archived object as not found
      - >-
        services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#refuses
        another tenant’s 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-002-06
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/integration/services/describe/describe-custom-object.integration.spec.js#lists
        the fixed standard fields, the publication pair among them, then the thirteen properties in display
        order
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Describe custom object

## 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.