ATS-PFM-OPS-005 Inspect background runs within customer reach: Capability Test Specification
Markdown Design / Platform / Operational Records / Background Work / Capability Test Specification Coverage Rule covered Transition not-applicable Validation covered Permission covered Edge gap: FND-PFM-OPS-057 Failure gap: FND-PFM-OPS-057 Boundary covered Concurrency gap: FND-PFM-OPS-057 Invariant covered Interaction covered Test Scenarios 10 scenarios proving CAP-PFM-OPS-005
01 Declare authorized read routes permission api test
Proves BR-CAP-PFM-OPS-005-01Preconditions The customer and workspace job routes are registered. Steps Inspect access, methods and permissions. Expected The routes require customer jobs-read authority and perform reads. Data Controlled records and caller contexts matching this scenario’s preconditions. Bound to Source services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js #declares the customer monitor and the tenant runs console, with platform.jobs.read 02 Hide a different customer’s job boundary api negative test
Proves BR-CAP-PFM-OPS-005-02Preconditions Two customers have job records. Steps List and open the other customer’s job through the customer monitor. Expected The foreign job is absent and its direct read matches an unknown-job response. Data Controlled records and caller contexts matching this scenario’s preconditions. Bound to Source services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js #says of another customer's job exactly what it says of an unknown one 03 Include workspace runs without customer attribution rule api test
Proves BR-CAP-PFM-OPS-005-03Preconditions The workspace has multiple services’ runs including a snapshot with no customer. Steps Read workspace runs and the customer-wide monitor. Expected The workspace read includes the snapshot while the customer-wide read excludes it. 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 #answers exactly the tenant's jobs, of every macroservice 04 Keep staff entry within its grant permission api negative test
Proves BR-CAP-PFM-OPS-005-04Preconditions Staff hold a grant into only one workspace and another caller belongs elsewhere. Steps Read the granted and ungranted workspace runs and customer monitor. Expected The allowed workspace is readable and the other requested surfaces are refused. 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 #is refused a tenant of the same customer the grant does not name 05 Refuse portal and anonymous inspection permission api negative test
Proves BR-CAP-PFM-OPS-005-05Preconditions A portal caller and an unauthenticated caller are available. Steps Request workspace runs. Expected Portal context is refused and anonymous access receives an authentication refusal. 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 #refuses a portal caller as a context mismatch 06 Validate list continuation and filters validation api negative test
Proves BR-CAP-PFM-OPS-005-06Preconditions Several runs support a paged list. Steps Page once and supply malformed cursor, status and kind values plus a well-formed unknown kind. Expected Valid continuation works, malformed values fail and the unknown kind returns no rows. Data Controlled records and caller contexts matching this scenario’s preconditions. Bound to Source services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js #refuses a cursor it did not issue 07 Omit private execution references invariant api test
Proves BR-CAP-PFM-OPS-005-08INV-DOM-PFM-OPS-001-12 Preconditions A settled job has a step catalog and events. Steps Read its snapshot and subsequent history. Expected Public detail omits execution handle and row version while later events follow the supplied sequence. Data Controlled records and caller contexts matching this scenario’s preconditions. Bound to Source services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js #never puts the execution handle or the row version on the wire 08 Enforce the Maintenance entry permission permission browser negative test
Proves BR-CAP-PFM-OPS-005-09Preconditions A reader has jobs authority and another does not. Steps Open Maintenance with both accounts. Expected Only the authorized account reaches Scheduled Jobs; the other sees Access Denied without its link. Data Controlled records and caller contexts matching this scenario’s preconditions. Bound to Source react-console:e2e/mock/maintenance-job-runs.mock.spec.ts #is the console's Access Denied state, and its link is not offered 09 Inspect the active workspace without job controls interaction browser test
Proves AS-JNY-PFM-OPS-001-01AS-JNY-PFM-OPS-001-02AS-JNY-PFM-OPS-001-03Preconditions The workspace has several services’ runs including a monthly snapshot. Steps Open Scheduled Jobs and inspect a row. Expected Workspace scope and month-specific subject are preserved and the panel has no start or stop action. Data Controlled records and caller contexts matching this scenario’s preconditions. Bound to Source react-console:e2e/mock/maintenance-job-runs.mock.spec.ts #lists the tenant's runs: what each was about, its status, and who started it ← Previous Capability Test Specification ATS-PFM-OPS-004 · Recover or deliberately stop background work: Capability Test Specification Next Capability Test Specification → ATS-PFM-OPS-006 · Investigate platform jobs in Rhythm HQ: Capability Test Specification