---
id: TST-PFM-SEC-110
title: Portal fixtures database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#the
      development fixtures: a portal fixture
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#while
      CRM’s functions are not installed
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#links
      no contact and answers none, so the bootstrap goes on
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#with
      CRM’s functions
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#links
      the contact CRM finds holding the fixture’s own address, and creates none
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#does
      not take a likely contact holding another address for the fixture’s own
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#has
      CRM create the fixture’s contact from its name and address when none holds it, and links it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#changes
      nothing on the next run: the same contact, and no second one created
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#refuses
      a console user, which links no contact
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#its
      tenant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#is
      reported missing when the tenant the fixture names is not provisioned
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#is
      not reported when the tenant exists
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js#is
      never asked of a console fixture
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite’s own dependency setup determines which external collaborators are controlled;
  registration alone does not certify them as live.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  The file has no scenario binding established by this examination. Its executable checks remain
  registered without assigning them broader acceptance coverage.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/dev-fixtures/portal-fixtures.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries: []
---
# Portal fixtures database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for portal fixtures.

## What This Suite Proves

The file supplies executable engineering checks for the named subject. No complete acceptance scenario is inferred from the file’s existence.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite’s own dependency setup determines which external collaborators are controlled; registration alone does not certify them as live.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.