---
id: TST-COM-CAT-136
title: Recommendation Rules Verification
kind: api-lifecycle
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js
implements:
  - ATS-COM-CAT-019-01
  - ATS-COM-CAT-019-02
  - ATS-COM-CAT-019-03
  - ATS-COM-CAT-019-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: 'Suite-owned workspace keys and database fixtures, removed by its cleanup hooks.'
binding_evidence:
  - scenario: ATS-COM-CAT-019-01
    source: >-
      services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#refuses
      an add_on rule with no products, 400 parameters_invalid
  - scenario: ATS-COM-CAT-019-02
    source: >-
      services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#refuses a
      binding to a placement that shows no such kind, 400 placement_unsupported
  - scenario: ATS-COM-CAT-019-02
    source: >-
      services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#refuses a
      cap above the placement’s, 400 max_offers_exceeds_placement
  - scenario: ATS-COM-CAT-019-03
    source: >-
      services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#refuses a
      rule whose action is start_journey, 409 action_unavailable: the journeys are R3’s
  - scenario: ATS-COM-CAT-019-04
    source: >-
      services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#moves
      through active, paused, active, ended, archived
  - scenario: ATS-COM-CAT-019-04
    source: >-
      services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#refuses
      to activate a rule bound to no placement, 409 no_placement
evidence:
  - 'services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js'
  - >-
    services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#Real: the
    composed handler, the routes, the mapper, the workflows, the persistence and PostgreSQL.
  - >-
    services-commerce:modules/recommendations/tests/e2e/recommendation-rules.e2e.spec.js#Doubled:
    the signing key pair, and Accounting's, CRM's and Platform's tables, which are local stand-ins.
execution_constraints:
  - No execution is performed in this documentation back-fill.
verification_boundary: >-
  Bindings identify the existing assertions contributing to each scenario; several suites can
  jointly cover a compound scenario.
---

# Recommendation Rules Verification

## Verification Boundary

The composed API handler runs locally with signed caller contexts and the integration database. Its route, mapping, permission and persistence assertions establish the local API boundary.

## What This Suite Proves

The recommendation rules assertions contribute to the scenarios listed in the register. Each binding retains its exact source test anchor so a reviewer can distinguish an individual contribution from the complete scenario.

## What It Does Not Prove

The register records source inspection only. It establishes no run result, delivery qualification or Product approval.

## Real Dependencies and Test Doubles

PostgreSQL and the services called by the suite are real. External service ports, file storage and queues may use the fixtures declared by the suite and its support helpers.

## Must Not Be Doubled

Keep the asserted database constraints, transactions, service functions and execution contexts real. For API suites, preserve the dispatcher and permission enforcement.