---
id: TST-ACC-TRX-327
title: Maintenance job runs suite
kind: browser-lifecycle
product_area: accounting
module: transactions
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/maintenance-job-runs.mock.spec.ts
implements: []
implements_parts: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: A browser context and suite-controlled mocked responses.
provenance: test
source: 'react-console:e2e/mock/maintenance-job-runs.mock.spec.ts'
evidence:
  - provenance: test
    source: 'react-console:e2e/mock/maintenance-job-runs.mock.spec.ts'
    assertion_titles:
      - Maintenance › Scheduled Jobs
      - is the only thing Maintenance holds
      - >-
        lists the tenant's runs: what each was about, its status, and who
        started it
      - filtering by job type narrows the list to that type
      - 'a row opens the run, read-only, in a drawer on the right'
      - Maintenance › Scheduled Jobs without platform.jobs.read
      - 'is the console''s Access Denied state, and its link is not offered'
      - Duplicate Rules and Integrations moved to Configuration
      - Duplicate Rules opens from Configuration › CRM
      - Integrations opens from the Connections section of Configuration
      - 'their old Maintenance URLs redirect, editor views and query kept'
    imports:
      - 'import path from "node:path"'
      - 'import { expect, test, type Page } from "@playwright/test"'
      - 'import { mockUrl, routes, urlPattern } from "../support/routes"'
    test_double_declarations:
      - ' * MOCK: Maintenance › Scheduled Jobs, the tenant''s job runs (Andrew, 2026-10-16), as the tenant administrator'
      - ' * (`?mockIdentity=customer`) against the MSW handlers in `mocks/handlers/tenant-jobs.ts`, which answer Platform''s'
      - 'import { mockUrl, routes, urlPattern } from "../support/routes"'
      - '  await page.addInitScript((value) => window.localStorage.setItem("rhythm.mock.identity", value), identity)'
      - '  await page.goto(mockUrl(routes.maintenance.scheduledJobs()))'
      - '    await page.goto(mockUrl(routes.maintenance.root()))'
      - '    await expect(page).toHaveURL(urlPattern(mockUrl(routes.maintenance.scheduledJobs())), { timeout: 60_000 })'
      - '    // Everything an administrator holds but the jobs read (`lib/security-context/mock-context.ts`).'
      - '    await page.addInitScript(() => window.localStorage.setItem("rhythm.mock.permissions", JSON.stringify(["crm.contacts.read"])))'
      - '    await page.goto(mockUrl(routes.maintenance.scheduledJobs()))'
      - '    await page.goto(mockUrl(routes.configuration.moduleArea("crm", "regions")))'
      - '    await expect(link).toHaveAttribute("href", mockUrl(routes.configuration.duplicateRules()), { timeout: 60_000 })'
      - '    await expect(page).toHaveURL(urlPattern(mockUrl(routes.configuration.duplicateRules())))'
      - '    await expect(breadcrumb.getByRole("link", { name: "CRM" })).toHaveAttribute("href", mockUrl(routes.configuration.module("crm")))'
      - '    await page.goto(mockUrl(routes.configuration.moduleArea("crm", "regions")))'
      - '    await expect(page).toHaveURL(urlPattern(mockUrl(routes.configuration.integrations())))'
      - '    await page.goto(mockUrl(routes.maintenance.area("duplicateRules")))'
      - '    await expect(page).toHaveURL(urlPattern(mockUrl(routes.configuration.duplicateRules())), { timeout: 60_000 })'
      - '    await page.goto(mockUrl(routes.maintenance.area("integrations", [], { q: "stripe" })))'
      - '    await expect(page).toHaveURL(urlPattern(mockUrl(routes.configuration.integrations([], { q: "stripe" }))))'
---

# Maintenance job runs suite

## Verification Boundary

The suite exercises console screens and their requests in a browser with controlled responses. Registration records the existing executable file; it does not report a run or establish product approval.

## What This Suite Proves

The executable assertions exercise this module, but no capability or feature scenario binding is established for this file. Its individual assertion titles remain in the evidence register for subsequent mapping.

## What It Does Not Prove

Controlled browser responses do not establish service authorization, database bounds, processor behavior or financial persistence. An unbound feature chain remains proposed, and this registration carries no execution result.

## Real Dependencies and Test Doubles

The real browser and console components run against suite-controlled data or responses. The evidence register identifies the mock setup; those returned values are assumptions of the screen test.

## Must Not Be Doubled

The screen components, their validation and their outgoing request construction are the verification boundary and must remain real. Service financial integrity needs an additional suite with real persistence.