---
id: TST-PFM-INT-594
title: automation rules
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/services/persistence/automation-rules.integration.spec.js
implements:
  - ATS-PFM-INT-020-01
  - ATS-PFM-INT-020-02
  - ATS-PFM-INT-020-05
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/services/persistence/automation-rules.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#creates
      the rule as a draft, owned by the event’s application, with its first version as the draft
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#edits
      the draft in place: the same version, its content replaced
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#publishes
      the draft as the current version and enables the rule
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#opens
      the next version as the draft once the last is published
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      to enable a draft rule, which only a publish enables (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#disables
      an enabled rule and enables it again
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#retires
      it
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      any move of a retired rule (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      a draft of a retired rule (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#replaces
      a never-published rule’s name and event, deriving its application again
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      to change a published rule’s event (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      a replacement at a stale version (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      a draft saved over a newer one (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#refuses
      to delete a published rule, which is retired instead (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#deletes
      a rule never published, with its draft
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js#answers
      404 for a rule the tenant does not have
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/workflow-actions/tests/integration/services/persistence/automation-rules.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# automation rules

## Verification Boundary

This database and service suite exercises automation rules. 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.