---
id: TST-PFM-NOT-118
title: query schedules dev
kind: browser-lifecycle
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/dev/query-schedules.dev.spec.ts
implements:
  - ATS-PFM-NOT-016-17
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
isolation: >-
  Run-specific fixture records and signed staff sessions in configured dev
  workspaces; cleanup owns only this run’s records.
assertion_bindings:
  - scenario: ATS-PFM-NOT-016-17
    suite: TST-PFM-NOT-118
    assertions:
      - 'react-console:e2e/dev/query-schedules.dev.spec.ts'
evidence:
  - 'react-console:e2e/dev/query-schedules.dev.spec.ts'
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence: []
---

# query schedules dev

## Verification Boundary

This browser suite exercises its configured console and service environment. Fixture availability and deployed routes can cause a skip; a present suite is not evidence of a successful run.

## What This Suite Proves

Its cases exercise select published scheduled-report content during schedule setup.

The registered scenario bindings identify the assertions this executable file contributes. They retain individual test references so that a composite scenario does not become a claim of complete execution by one file.

## What It Does Not Prove

A browser assertion about a retained status does not prove external provider delivery or every guard in the capability specification. Conditional setup checks prove only the branch that executes. No fresh execution or conformance result is claimed.

## Real Dependencies and Test Doubles

The suite uses the configured dev console, signed accounts and service endpoints. Notification acceptance journeys can also invoke local Platform assertion cases; those embedded cases retain their own database and adapter boundary.

## Must Not Be Doubled

The console action, service response and assertions for the tested workflow must remain real. Embedded Platform cases must retain the lifecycle logic and database constraints that their assertions inspect.