---
id: TST-PFM-OPS-054
title: Hq ops
kind: browser-lifecycle
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/hq-ops.mock.spec.ts
implements:
  - ATS-PFM-OPS-004-06
  - ATS-PFM-OPS-006-03
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: A browser context and controlled fixture responses.
evidence:
  - >-
    react-console:e2e/mock/hq-ops.mock.spec.ts at baf6dae382d6f41dce976c7f848667ccc37e076f: existing
    suite body, setup, assertions and cleanup.
binding_note: Bindings apply only to the listed specification scenarios.
assertion_sources:
  - >-
    react-console:e2e/mock/hq-ops.mock.spec.ts#shows the overview, its sandboxes and the sender's DNS
    records
  - >-
    react-console:e2e/mock/hq-ops.mock.spec.ts#says so when the tenant sends from the shared Rhythm
    sender
  - >-
    react-console:e2e/mock/hq-ops.mock.spec.ts#says sender identities are coming, without an error, where
    Platform does not serve the route yet
  - >-
    react-console:e2e/mock/hq-ops.mock.spec.ts#the edit sheet saves, has no identifier to change, and
    confirms before disabling the tenant
  - 'react-console:e2e/mock/hq-ops.mock.spec.ts#says so when the tenant doesn''t exist'
  - 'react-console:e2e/mock/hq-ops.mock.spec.ts#is opened from the tenants list''s row menu'
  - 'react-console:e2e/mock/hq-ops.mock.spec.ts#walks every step and lands on the job it started'
  - >-
    react-console:e2e/mock/hq-ops.mock.spec.ts#creates a new customer with a customer ID that follows the
    tenant ID until it is edited
---

# Hq ops

## Verification Boundary

This suite exercises application licensing through the console browser flow. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The jobs portion checks running and failed detail, confirmation of provisioning retry, queued and missing states, and navigation from the staff list using controlled responses. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

Controlled responses do not prove the real service supplies the same result. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The console and browser are real. Controlled responses or mock handlers replace service behavior; they do not establish deployed API conformance.

## Must Not Be Doubled

The console interaction and displayed result under assertion remain real.