--- id: TST-PFM-MTD-049 title: custom apps kind: api-lifecycle product_area: platform module: metadata revision: 1 status: draft source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 repository: services-platform files: - modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js implements: - ATS-PFM-MTD-010-03 - ATS-PFM-MTD-010-04 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/custom-objects/tests/e2e/custom-apps.e2e.spec.js' - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#creates an app, answering it with no objects yet - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 to a create whose id is the key of a platform application - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 to a create whose label is blank, as required - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 to a create naming a property the app does not have - 'services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#reads an app by its key' - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 404 for an app the tenant does not have - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#replaces an app with the record read back, at its version - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 409 to a replacement at a stale version - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 to a replacement that changes archived, which only archive and restore change - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#archives an app, then restores it - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 409 to archiving an archived app - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#lists the apps in display order, filtered by archived on request - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 to an archived filter that is neither true nor false - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 401 to a call with no context - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#lets a caller who may only read list and read apps - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 403 to a create by a caller who may only read - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 403 to a replacement by a caller who may only read - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 403 to an archive and a restore by a caller who may only read - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 403 to a context of another tenant, which the path cannot reach - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers the placement on the object - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#lists the app with the active object placed in it, its group and its staff access - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#reads the app with the same placed object - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#leaves a draft object placed in the app out of its objects - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#describes the object with its placement - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#describes an object that is placed nowhere with no placement property - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#places an object in a platform application - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 naming an app that does not exist - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 400 to a new placement in an archived custom app - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 409 to archiving an app an active object is placed in, naming it, and the app stays listed with it (B3) fixture_imports: - chai - ../../../../aws/api/platform-api-handler - '@rhythmsoftware/macroservice-testing/signed-context' - '@rhythmsoftware/macroservice-execution/tenant-time-zones' - '@rhythmsoftware/macroservice-testing/stage' - ../../../tenants/services/persistence/tenants - ../../../metadata/aws/api/metadata.routes - ../../aws/api/custom-objects.routes - ../integration/support test_doubles: [] limitations: [] unmatched_specification: null binding_assertions: - scenario: ATS-PFM-MTD-010-03 provenance: test source: - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 409 to a replacement at a stale version note: >- These references identify the assertions this suite contributes; bindings to additional suites remain part of the scenario’s proof. - scenario: ATS-PFM-MTD-010-04 provenance: test source: - >- services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#answers 409 to archiving an app an active object is placed in, naming it, and the app stays listed with it (B3) note: >- These references identify the assertions this suite contributes; bindings to additional suites remain part of the scenario’s proof. --- # Custom apps ## Verification Boundary This API suite checks custom objects and records 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.