---
id: TST-PFM-OPS-061
title: View history
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/audit/tests/integration/services/record-views/view-history.integration.spec.js
implements:
  - ATS-PFM-OPS-009-02
  - ATS-PFM-OPS-009-03
  - ATS-PFM-OPS-009-05
  - ATS-PFM-OPS-009-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: >-
  The prepared local test database and suite-owned identifiers; existing hooks control rollback or
  cleanup.
evidence:
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js
    at ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: Bindings apply only to the listed specification scenarios.
assertion_sources:
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#answers
    the endpoint’s default page when the caller asks for no size
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#answers
    a cursor while there is more history
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#answers
    the newest event first
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#answers
    every element of an event, including the metadata it was recorded with
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#answers
    the largest page a caller may ask for
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#refuses
    a page larger than the maximum, naming it
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#refuses
    a page of nothing
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#pages
    the whole history in sevens with no gap and no repeat
---

# View history

## Verification Boundary

This suite exercises record activity through production operations against the local database. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks page an actor’s stored visits, validate sizes and filters, preserve entries after target removal and exclude other actors or workspaces. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database and production operations under test are real. The suite controls time where boundary checks require it.

## Must Not Be Doubled

The persistence operations, database constraints and reads under assertion remain real.