---
id: TST-PFM-SEC-171
title: Workspace portal onboarding jobs.queries 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/persistence/tenant-portal-onboarding-jobs.queries.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/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#security
      persistence reads: tenant portal onboarding jobs
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#getTenantPortalOnboardingJob
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      every field of an onboarding nothing has happened to but its submission, the stack columns
      still empty
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      the stack, the template version and the pool a failed onboarding got as far as, whole
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#carries
      the job contract’s instants as Moments, not as the text the driver sent
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      nothing for an id of the right grammar that names no onboarding
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#listTenantPortalOnboardingJobs
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      the tenant’s onboardings newest first, each record whole
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      only that tenant’s onboardings: another tenant’s list is empty
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      at most the page size asked for, the first page of the same order
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      an empty list for a page size of none at all
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#findOpenTenantPortalOnboarding
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      the whole unfinished onboarding, which is what a second request for the portal is answered
      with
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#is
      blind to the onboarding that already failed, which is how the tenant could have a second one
      at all
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js#answers
      nothing for a tenant nobody ever asked a portal for
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls workflow execution at the declared seams; those collaborators remain outside
  its live proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/persistence/tenant-portal-onboarding-jobs.queries.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/persistence/tenant-portal-onboarding-jobs.queries.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - workflow execution
---
# Workspace portal onboarding jobs.queries 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 workspace portal onboarding jobs.queries.

## 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 controls workflow execution at the declared seams; those collaborators remain outside its live proof.

## 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.