ATS-ACC-BAT-009 Configure recurring batch streams: Capability Test Specification
Markdown Design / Accounting / Batch Management / Recurring intake and assignment / Capability Test Specification Coverage The scenarios define focused checks for this outcome. The coverage map distinguishes specified checks from unresolved proof; executable bindings identify inspected assertions and carry no execution result.
Deleting unused intake clears the stream. Inactive intake survives until reactivation. Routing references prevent stream removal. Reactivation and rolling have distinct posting effects. These checks use the related capability’s outcome as part of the setup or verification. Unbound interactions remain proposed until a suite executes the complete chain.
Coverage Rule covered Transition gap: FND-ACC-BAT-063 Validation covered Permission gap: FND-ACC-BAT-063 Edge gap: FND-ACC-BAT-063 Failure gap: FND-ACC-BAT-063 Boundary covered Concurrency covered Invariant covered Interaction covered Test Scenarios 17 scenarios proving CAP-ACC-BAT-009
01 Recurring ownership and schedule identity stay fixed invariant api negative test
Proves BR-CAP-ACC-BAT-009-01INV-DOM-ACC-BAT-001-09 Preconditions A recurring configuration belongs to the selected unit. Steps Replace it with another unit and directly change its unit or schedule reference. Expected Replacement returns 409; both direct changes trigger the database immutability refusal. Data Provide two units. Bound to Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers 409 to a change of business unit 02 Creation validates schedule and reference rule api negative test
Proves BR-CAP-ACC-BAT-009-02Preconditions No special setup is necessary. Steps Omit the schedule, create Daily credit cards without a reference and repeat that creation. Expected The omission identifies schedule; allocation produces daily_credit_cards; reuse identifies the conflicting reference. Data Provide no fixtures beyond the stated setup. Bound to Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers 400 naming schedule to a body without one 04 Templates accept only the supported language and variables validation api negative test
Proves BR-CAP-ACC-BAT-009-04Preconditions No special setup is necessary. Steps Submit invalid Liquid, an unknown code-template variable and an earlier-product template. Expected Each 400 identifies the affected template field. Data Provide no fixtures beyond the stated setup. Bound to Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers 400 naming batch_code_template to a template using a variable a batch template does not provide 05 Activation attempts immediate intake transition api negative test
Proves BR-CAP-ACC-BAT-009-06Preconditions One unit covers today in its calendar and another does not. Steps Create active configurations in both, then deactivate and reactivate the first. Expected The valid unit receives today’s Open batch; the other retains a first-batch refusal without a batch; reactivation attempts a new first batch. Data Provide fiscal years. Bound to Source services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js #saves a recurring batch whose first batch is refused, with the refusal and no batch 06 Inactive recurrence leaves current intake usable interaction api test
Proves BR-CAP-ACC-BAT-009-07Preconditions An active configuration has an Open batch and a schedule paused after five failures. Steps Deactivate the configuration, inspect its next run, then reactivate and inspect scheduling again. Expected Deactivation removes the next run; reactivation restores scheduling and clears the pause and failure count. Data Provide assignment settings naming the recurring batch. Bound to Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers no next run once deactivated 07 Replacement requires the current version concurrency api negative test
Proves BR-CAP-ACC-BAT-009-08Preconditions The configuration currently rolls in late afternoon. Steps Replace it with a later time using the current version, then the old version and then no version. Expected The first updates scheduling and its description; stale and absent versions return 409 and 400. Data Provide no fixtures beyond the stated setup. Bound to Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers 409 StaleObject to a replacement at the version first read 08 Assignment references prevent deletion interaction api negative test
Proves BR-CAP-ACC-BAT-009-09INV-DOM-ACC-BAT-001-11 Preconditions The default and two ordered assignment rules reference the configuration. Steps Delete the recurring configuration. Expected A 409 identifies the default and rule positions and retains its schedule. Data Provide batch assignment settings. Bound to Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers 409 naming the settings and how they name it 11 Application and write access are distinct permission api negative test
Proves BR-CAP-ACC-BAT-009-12Preconditions A reader can use Accounting while another principal lacks application access. Steps As the reader, list, read, inspect runs and preview, then create, replace and delete; as the other principal, list. Expected Reader requests succeed only for reads; writes return permission 403 and the other principal receives application-access 403. Data Provide security fixtures. Bound to Source services-accounting:modules/batches/tests/e2e/batches-security.e2e.spec.js #is refused the create 403 permission_missing 17 Recurring pagination exposes the supported maximum boundary api negative proposed
Proves BR-CAP-ACC-BAT-009-13Preconditions An isolated unit owns two hundred one matching recurring configurations. Steps Request a page of two hundred, follow its cursor and request more than the supported limit. Expected The first page contains two hundred distinct records and the next contains the remaining record; oversized requests never return more than two hundred records. Data Owned records in an isolated workspace with the stated calendar and accounting setup. Source services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js #answers 400 to a limit above 200 ← Previous Capability Test Specification ATS-ACC-BAT-008 · Bring waiting batches to the posting team’s attention: Capability Test Specification Next Capability Test Specification → ATS-ACC-BAT-010 · Advance a scheduled stream and post its predecessor: Capability Test Specification