--- id: TST-PFM-INT-588 title: workflow actions tables kind: integration product_area: platform module: integrations revision: 1 status: draft source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f repository: services-platform files: - modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js implements: - ATS-PFM-INT-019-04 - ATS-PFM-INT-020-02 - ATS-PFM-INT-020-04 - ATS-PFM-INT-022-01 environment: local implementation_state: implemented latest_result: not-run latest_run_at: null latest_run_ref: null conformance: not-verified estimated_minutes: 5 isolation: >- Use the suite-owned database fixtures and its declared cleanup; prepare the test database before integration or lifecycle execution. evidence: - >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js test_cases: - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#accepts a trigger point whose qualified key is its application and key (the negative control) provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a qualified key that is not its application and key provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a trigger point key outside the library’s grammar provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a host kind outside its grammar provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses facts that are not a JSON object provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a retired point that is still active provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a second point of one host and key provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#accepts an action type of the manifest’s shape (the negative control) provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses an execution outside inline, durable and host provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a host type that names no host provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses an action type configurable on no host provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a params schema over 64 KiB provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a second draft of one rule provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#accepts an edit of the draft (the negative control) provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses actions that are not a JSON array provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#accepts the publication itself, an update of the draft provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a change to a published version’s actions provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a change to a published version’s condition provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a change to a published version’s condition hash provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses withdrawing a published version’s publication provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#still accepts a change to a published version’s system columns provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#accepts 400 holidays (the negative control) provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses 401 holidays provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a weekday outside 1 to 7 provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses no working day provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses a second default of one tenant provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#accepts a default of another tenant beside it provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#refuses an inactive default provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#forces the tenant policy on the five tenant tables, one policy each provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#leaves the four platform-wide tables without a tenant and without a policy, as the register records provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#shows the tenant its own template, with no predicate in the statement (the premise) provenance: test - source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js#shows another tenant nothing of it provenance: test dependency_evidence: provenance: test source: >- services-platform:modules/workflow-actions/tests/integration/db/workflow-actions-tables.integration.spec.js reviewed: - Suite introduction - Fixture setup - Client substitutions - Assertions and cleanup --- # workflow actions tables ## Verification Boundary This database and service suite exercises workflow actions tables. Its registration records the executable definition; no run result is asserted. ## What This Suite Proves The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario. ## What It Does Not Prove In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied. ## Real Dependencies and Test Doubles The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path. ## Must Not Be Doubled The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.