---
id: TST-PFM-QRY-270
title: Platform current user criterion
kind: integration
product_area: platform
module: queries
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464
repository: services-platform
files:
  - modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js
implements:
  - ATS-PFM-QRY-002-08
  - ATS-PFM-QRY-008-10
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: 'The suite’s database fixtures, controlled execution contexts and file-owned external dependency seams.'
evidence:
  - >-
    services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js
assertion_bindings:
  - scenario: ATS-PFM-QRY-002-08
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js#answers
        the caller their own tasks, with their own id in the row
      - >-
        services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js#answers
        a second caller their own tasks, from the very same criterion
      - >-
        services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js#refuses
        the token on a field whose owner does not say it holds a user, naming the field
      - >-
        services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js#refuses
        the token under an operator that compares no user, naming the operator
      - >-
        services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js#refuses
        an execution that is nobody in particular, rather than answering it nothing
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-008-10
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/execute/current-user-criterion.integration.spec.js#refuses
        at registration the same recipe written on a field that holds no user, naming the field
    scope: assertions cited by the scenario
    provenance: test
fixture_seams: []
---

# Platform current user criterion

## Verification Boundary

The file invokes its service or persistence boundary against local integration fixtures.

## What This Suite Proves

Its assertions check current user criterion. The assertion bindings identify the corresponding acceptance examples and retain their original test-title citations.

## What It Does Not Prove

Local execution does not establish deployed queue scheduling, every external provider response or a passing result at the pinned revision.

## Real Dependencies and Test Doubles

The integration fixture and any imported dependency seams define the environment. Database-oriented checks use PostgreSQL; file-owned transport, clock, provider or worker seams isolate the explicitly controlled boundary.

## Must Not Be Doubled

Keep the service or persistence operation whose behavior is asserted real. Database constraints and transactions cannot be replaced by fixture answers when they are the subject of the check.