Rhythm 2.0 Specifications

Appearance

ATS-ACC-PRD-013Record the follow-up work a purchase needs: Capability Test Specification

Markdown

ATS-ACC-PRD-013

Record the follow-up work a purchase needs: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-ACC-PRD-013

Design

Executed by
TST-ACC-PRD-006, TST-ACC-PRD-027, TST-ACC-PRD-039

KindAcceptance test setProduct areaAccountingModuleProductsRevision3

Read atservices-accounting f47cb263react-console baf6dae3

Record the follow-up work a purchase needs: Capability Test Specification ​

Coverage ​

The frontmatter lists a proof scenario or finding for every required rule and records each applicable category. Scenario coverage describes what to check; bindings identify the assertions that already exist, and execution results remain unverified. Task-name and delay endpoints, exact maximum-size success, full permission refusal and concurrent replacements need execution; task creation belongs to the purchasing consumer. Workflow edges not named by a scenario remain in this finding rather than gaining a binding from shared workflow membership.

A console correction preserves task instructions. An API-created product has one active CRM task instruction. Rename it in the console and deactivate it from the list; read its task instructions after each save. The task instruction remains unchanged and the saved product versions advance.

Coverage

  • Rule covered
  • Transition gap: FND-ACC-PRD-062
  • Validation covered
  • Permission gap: FND-ACC-PRD-062
  • Edge gap: FND-ACC-PRD-062
  • Failure gap: FND-ACC-PRD-062
  • Boundary covered
  • Concurrency gap: FND-ACC-PRD-062
  • Invariant gap: FND-ACC-PRD-062
  • Interaction covered

Test Scenarios

5 scenarios proving CAP-ACC-PRD-013; 5 bound to an existing test.

01 Task references respect CRM status and scopevalidationunitnegativetest
Proves
BR-CAP-ACC-PRD-013-02 INV-DOM-ACC-PRD-001-15
Preconditions
CRM fixtures include active, inactive and foreign-workspace types and queues.
Steps
Try new invalid assignments and resave instructions holding later-inactive references.
Expected
New invalid choices fail while retained choices survive.
Data
CRM fixtures include active, inactive and foreign-workspace types and queues.
Bound to
services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#keeps a task type and a queue that became inactive while the product held them
Source
services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#keeps a task type and a queue that became inactive while the product held them
02 Assignee format differs from existencevalidationapinegativetest
Proves
BR-CAP-ACC-PRD-013-03
Preconditions
A product has task instructions.
Steps
Submit an assignee value that is a plain name rather than a user identity.
Expected
The API and database reject the invalid identity format.
Data
A product has task instructions.
Bound to
services-accounting:modules/products/tests/e2e/product-features.e2e.spec.js#refuses an assignee that is not a Platform user id
services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#refuses an assignee that is not a Platform user id by the database’s check
Source
services-accounting:modules/products/tests/e2e/product-features.e2e.spec.js#refuses an assignee that is not a Platform user id
03 Task lists replace within their boundboundaryunitnegativetest
Proves
BR-CAP-ACC-PRD-013-04
Preconditions
A product supports task fixtures.
Steps
Submit twenty-one task instructions.
Expected
The oversized collection is refused.
Data
A product supports task fixtures.
Bound to
Source
services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#refuses more than 20 tasks to generate
04 Complete task instructions survive a readruleapinegativetest
Proves
BR-CAP-ACC-PRD-013-01
Preconditions
The workspace provides active task types and queues.
Steps
Create instructions with name, description, queue, assignee and due delay, then retrieve the product.
Expected
Each supported instruction value and submitted order reads back.
Data
The workspace provides active task types and queues.
Bound to
Source
services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#answers every feature as written, the lists in the order sent
05 A console correction preserves task instructionsinteractionbrowsernegativetest
Proves
BR-CAP-ACC-PRD-013-04 BR-CAP-ACC-PRD-004-10
Preconditions
An API-created product has one active CRM task instruction.
Steps
Rename it in the console and deactivate it from the list; read its task instructions after each save.
Expected
The task instruction remains unchanged and the saved product versions advance.
Data
An API-created product has one active CRM task instruction.
Bound to
Source
services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#refuses more than 20 tasks to generate; react-console:lib/accounting-config/product-form.ts:formToWrite

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