Test Cases · Requirement artifact
SPECIRA
Test Cases Export: Assignment Recommendations
Meridian Field Services: instructional example, not project evidence
Draft · watermark policy: draft_only
template test_cases v2 · pack: specira_default_delivery
frozen copy; the register is the source of truth
§1
Export Scope & Snapshot
mandatory
1 decision1 evidence rule
validators: export_carries_generation_timestamp_and_scope · every_id_resolves_to_register_record
An export without a scope statement is not evidence. This header is what
lets an auditor trust the rest.
Frozen copy: September 18, 2026, 16:40
Point-in-time export of the
test-case register[1], generated for the
US-3 acceptance milestone
(
sign-off record[2]). The register
remains live; this document is the audit record of this moment.
Scope:
requirement, assignment recommendations; suites, board-suggestions, override, shortfall,
mobile-confirm; environments, pilot (Toronto) per bindings.
Excludes:
cutover-slice cases (ERR-05, deferred:
decision[6]). Every id resolves to
its live record.
§2
Test Case Register (Exported View)
mandatory
index of register decisions; nothing decided here
validators: case_steps_reference_outline_not_restate · automation_status_enum_requires_pointer_when_automated · no_embedded_run_history
Steps are references: the FRD outline plus the story row this case
executes; copied Given/When/Then fails review here exactly as it does in a story. Run
SUMMARIES only; full evidence attaches to the package.
Suite: override (mirrors the register grouping)
TC-311Override records with
reasonautomated
Preconditions JOB-2214 open, three
suggestions rendered, T-088 on shift outside them.
Expected Assignment records T-088 with RC-03; T-088 notified;
override logged.
Automation
board-suite/override.spec cases 1 to 4:
CI board-suite job[7].
Last run: pass · Sep 18 · pilot.
TC-313Note boundary honored
(250 / 251)automated
priority: mediumowner: K. Yamada
Expected 250 records in full; 251 rejected naming the limit.
Suite: shortfall
TC-322Shortfall names the
countmanual
priority: mediumowner: K. Yamada
pointer: none · visual notice check, reason recorded
Last run pass Sep 18, after the US-7 kickback re-entry.
Flagged exception: the one case without an outline
TC-341 (exploratory feed-jitter probe) carries prose steps,
flagged
no-outline with its FRD change-request link
(
change requests[3]): visible, never
silent.
§3
Edge-Case Coverage Matrix
mandatory
1 decision1 evidence rule
validators: coverage_matrix_cells_hold_ids_never_prose · empty_cells_carry_disposition
Path classes against statements, ids in cells. An empty cell is a visible
absence with a disposition: covered elsewhere, deferred with rationale, or a named gap.
| Statement | Happy | Negative | Boundary | Edge | Corner |
| FR-010 | TC-301 · TC-306 | none |
none | TC-307 |
deferred to slice 3 by decision
(slice plan[6]) |
| FR-011 | none | none |
TC-302 · TC-303 | none |
| FR-012 | TC-311 |
TC-312 | TC-313 |
TC-314 |
| FR-013 · ERR catalog | none |
TC-304 · TC-305 · TC-321..323 · TC-331..332 |
none | none |
ERR-05 row: excluded by export scope, stated in §1. No cell is
silently empty.
§4
Environment Bindings
conditional · engaged: UI-facing
1 decision1 evidence rule
validator: environment_binding_declared_when_ui_facing
| Configuration | Suites bound | Last-run summary |
| Desktop Chrome current · Desktop Edge current |
board-suggestions · override · shortfall |
Converge: one summary, pass Sep 18 |
| iOS Safari · Android Chrome |
mobile-confirm (TC-316/317) |
Android: one divergent slow-notification run, re-run pass; noted per
configuration |
Set inherited from experience constraints[8]
and the strategy ladder, trimmed to pilot scope; trim rationale recorded.
§5
Acceptance Layers (Pointer)
mandatory · pointer only
validator: acceptance_pointer_links_resolve_zero_content
Outlines: the FRD[3] (the only
Given/When/Then anywhere). Concrete rows:
the story set[2]. Executable definitions
and run history: the register[1] this
document exports. Nothing acceptance-shaped is written here; a criterion authored in this
artifact would be the fourth authoring place the model forbids.
§6
Open Questions
mandatory1 decision
| Question | Owner | Answer by | Blocks |
| Does the exploratory feed-jitter probe TC-341 graduate
to an outlined case once its FRD change request lands? |
K. Yamada | Oct 2, 2026 |
TC-341's automation only |
Omission note (backend-only scope): "§4 Environment Bindings omitted:
API-only requirement, no user-facing configurations. Rationale recorded in adaptation
event #1."
Refs
References & Package Contents
In this export package
package
[3] Functional spec: outlines AC-010..012, ERR catalog, change requests
./frd-recommendation-rules.docx
package
[4] US-3 acceptance run export: full evidence
./acceptance-runs/us-3-run-2026-09-18.html
In the Specira workspace
specira
[1] Test-case register: the live source of truth this document freezes
app.specira.ai/projects/dispatch-modernization/test-cases
specira
[2] Story set: AC rows, sign-off record, defects
app.specira.ai/projects/dispatch-modernization/artifacts/user-stories
specira
[5] Risk register: assignment integrity
app.specira.ai/projects/dispatch-modernization/risks
specira
[6] Decisions: pilot cutover plan, slice plan
app.specira.ai/projects/dispatch-modernization/decisions
specira
[7] CI: board-suite job
app.specira.ai/projects/dispatch-modernization/ci/board-suite
specira
[8] PRD: experience constraints
app.specira.ai/projects/dispatch-modernization/artifacts/prd