---
id: TST-PFM-NOT-119
title: Operational Slack provider delivery
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/notifications/tests/provider/slack-system.provider.spec.ts
implements:
  - ATS-PFM-NOT-013-11
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: >-
  One operational provider-test message in the configured development operations
  channel.
evidence:
  - >-
    services-platform:modules/notifications/tests/provider/slack-system.provider.spec.ts
verification_note: >-
  This suite sends one real development message through the operational adapter;
  it does not exercise publication, request processing or provisioning
  producers.
---

# Operational Slack provider delivery

## Verification Boundary

This suite sends one real development message through the operational adapter; it does not exercise publication, request processing or provisioning producers.

## What This Suite Proves

The executable case exercises post an operational payload to the configured provider.

## What It Does Not Prove

The suite does not establish the entire feature chain or a fresh execution result. Its retained assertions apply only within the stated dependency boundary.

## Real Dependencies and Test Doubles

Development Secrets Manager, the real secret client, renderer, adapter and Slack are real. Only the execution logger is a test context.

## Must Not Be Doubled

The secret lookup, adapter and Slack provider must remain real.