---
id: TST-PFM-INT-596
title: business calendars
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/business-calendars.integration.spec.js
implements:
  - ATS-PFM-INT-019-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/services/persistence/business-calendars.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#answers
      the first as written, every property
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#stores
      the working days in weekday order
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#clears
      the first’s default in the same write, moving its version
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#answers
      the second as the tenant’s default
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#replaces
      it at its version, clearing its hours
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#deletes
      it
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      a time zone that is not an IANA name
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      no working day
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      a weekday outside 1 to 7
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      a weekday listed twice
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      working hours that end before they start
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      a time of day that is not HH:MM
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      a holiday that is not a date
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      more than 400 holidays
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#accepts
      exactly 400 holidays (the cap’s negative control)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      an inactive default
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      an id the tenant already uses (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses
      a replacement at a stale version (409)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#is
      refused (the premise)
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#leaves
      the tenant’s default where it was
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#inserts
      it once, and adopts it the second time
    provenance: test
  - source: >-
      services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#makes
      it Monday to Friday, 09:00 to 17:00, no holidays, the tenant’s zone and its default
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# business calendars

## Verification Boundary

This database and service suite exercises business calendars. 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.