Rhythm 2.0 Specifications

Appearance

ATS-PFM-OPS-007Inspect jobs across Rhythm services: Capability Test Specification

Markdown

ATS-PFM-OPS-007

Inspect jobs across Rhythm services: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-OPS-007

Design

Executed by
TST-PFM-OPS-066, TST-PFM-OPS-074, TST-PFM-OPS-076, TST-PFM-OPS-078

KindAcceptance test setProduct areaPlatformModuleOperational RecordsRevision2

Read atservices-platform ad3f6a65macroservice-libraries 54536a44react-console baf6dae3

Inspect jobs across Rhythm services: Capability Test Specification ​

Coverage ​

The category map distinguishes authored scenarios from unresolved proof obligations. A bound scenario names an existing executable suite; its recorded result remains unrun.

RuleProof status
BR-CAP-PFM-OPS-007-01ATS-PFM-OPS-007-01, ATS-PFM-OPS-007-08
BR-CAP-PFM-OPS-007-02ATS-PFM-OPS-007-02
BR-CAP-PFM-OPS-007-03ATS-PFM-OPS-007-03, ATS-PFM-OPS-007-07
BR-CAP-PFM-OPS-007-04ATS-PFM-OPS-007-04
BR-CAP-PFM-OPS-007-05ATS-PFM-OPS-007-05
BR-CAP-PFM-OPS-007-06ATS-PFM-OPS-007-06

Inspect a second service within workspace reach. The shared monitor preserves the owner’s description and the caller’s workspace reach.

Follow a published run from the staff list. Staff can follow the published record without modifying the owner’s run.

Evidence and Boundaries ​

Pinned assertion sources support the listed executable bindings. Proposed cases retain the proof required beyond those boundaries. Structured obligations name incomplete object, transition and permission trace; row-level concurrency proof does not establish complete workflow serialization.

Coverage

  • Rule covered
  • Transition not-applicable
  • Validation covered
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-OPS-059
  • Boundary gap: FND-PFM-OPS-059
  • Concurrency gap: FND-PFM-OPS-059
  • Invariant covered
  • Interaction covered

Test Scenarios

8 scenarios proving CAP-PFM-OPS-007; 6 bound to an existing test.

01 Continue one list across publishersruleapitest
Proves
BR-CAP-PFM-OPS-007-01
Preconditions
A compatible second service publishes a merge job alongside Platform work.
Steps
List, count and paginate across their jobs.
Expected
Both services participate in a shared order and continuation.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#pages across the two macroservices, the cursor of one continuing into the other
02 Exclude unpublished familiesvalidationapinegativetest
Proves
BR-CAP-PFM-OPS-007-02
Preconditions
A schema stores a job without publishing views.
Steps
List and open its job.
Expected
The job is unavailable to the shared reader.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#does not find a schema that holds the same job and publishes no view
03 Apply scope to another service’s jobpermissionapinegativetest
Proves
BR-CAP-PFM-OPS-007-03
Preconditions
A published merge job belongs to one customer.
Steps
Read it with allowed and foreign customer contexts.
Expected
Only the allowed context receives its snapshot and published step definition.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#applies the caller’s scope to it, as to a job of Platform’s own
04 Use the owner’s subject wordingruleapitest
Proves
BR-CAP-PFM-OPS-007-04
Preconditions
A merge and monthly snapshot are published.
Steps
List them within and across workspaces.
Expected
The merge uses its owner’s wording and only the workspace snapshot subject includes its month.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/jobs/tests/e2e/jobs-tenant-runs.e2e.spec.js#names the snapshot run by its snapshot alone when the list is read across tenants
05 Provide a fallback labeledgeunittest
Proves
BR-CAP-PFM-OPS-007-05
Preconditions
One kind is cataloged and another is unfamiliar.
Steps
Resolve both display labels.
Expected
The known label remains and the unfamiliar kind receives readable service-based attribution.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/jobs/tests/unit/job-kind-labels.spec.js#humanises an unknown kind and attributes it to the application of its schema
06 Keep views aligned with registered kindsinvariantunitnegativetest
Proves
BR-CAP-PFM-OPS-007-06
Preconditions
The Platform registry and latest view migration are available.
Steps
Compare kind branches and generated view definitions.
Expected
All registered kinds remain represented and the migration matches the builders.
Data
Controlled records and caller contexts matching this scenario’s preconditions.
Bound to
Source
services-platform:modules/jobs/tests/unit/cross-job-query.view.spec.js#registers exactly the Platform job kinds, so none is invisible to the reconciler
07 Inspect a second service within workspace reachinteractionapiproposed
Proves
BR-CAP-PFM-OPS-005-03 BR-CAP-PFM-OPS-007-03
Preconditions
A second service publishes a workspace run with a step catalogue.
Steps
List the workspace runs, open the second service run, and request its events.
Expected
The shared monitor preserves the owner’s description and the caller’s workspace reach.
Data
Isolated workspace records and caller contexts for both sides of the interaction.
Source
services-platform:modules/jobs/tests/e2e/jobs-tenant-runs.e2e.spec.js#answers exactly the tenant's jobs, of every macroservice; services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#applies the caller’s scope to it, as to a job of Platform’s own; CAP-PFM-OPS-005; WF-PFM-OPS-007
08 Follow a published run from the staff listinteractionapiproposed
Proves
BR-CAP-PFM-OPS-006-01 BR-CAP-PFM-OPS-007-01
Preconditions
A compatible second service publishes a run for a customer.
Steps
Find the run in HQ and open its timeline and event history.
Expected
Staff can follow the published record without modifying the owner’s run.
Data
Isolated workspace records and caller contexts for both sides of the interaction.
Source
services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js#refuses a console caller of the job’s own customer the HQ route as 403; services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#pages across the two macroservices, the cursor of one continuing into the other; CAP-PFM-OPS-006; WF-PFM-OPS-007

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software