Progress is stored on the server: use Save to server to persist your edits, and they are reloaded automatically the next time this page opens. Export JSON / Import JSON remain available as a manual fallback. The case inventory is loaded from data.json (serve the files over HTTP / host online).
Elaboration funnel
Cumulative progress of cases through Planned → Elicited → In Review → Validated → Created.
Lifecycle states
What each test-case state means in the elaboration workflow.
Coverage by functionality group
State composition per group (bar width proportional to case count).
Coverage by batch
State distribution per delivery batch.
Coverage by execution form
Elaboration state by Manual / Manual assisted by application / Automatic (the Manual's three values). Provisional mapping: both former "Semi-automated" and "Automated" cases are recorded as Manual assisted by application — in the reviewed artifacts no case qualified as Automatic, which stays empty until test-application instrumentation exists (per changelog E3). Per-case forms are revised as each batch is reviewed.
Deliveries
Elaboration deliveries by date (each on a Friday): completed deliveries plus the projected weekly schedule (one batch per Friday) until the suite is complete. Dates are milestones, not contractual deadlines.
Description roadmap by batch
Described (already specified) vs only-planned cases, per delivery batch and aligned month.
Description status by group
How many cases are already described vs still planned, per functionality group.
Execution results
Distribution of executed cases by result.
Results by group
Passed, failed and blocked among executed cases per group.
Results by batch
Case registry & editing
Change the state and result of each case. Edits update the coverage and execution views immediately.
ID
B
Group
Case
Exec.
State
Result
Notes
States: Planned · Elicited · In Review · Validated · Created. Result applies to created cases. Exec. = execution form (Manual / Manual assisted by application / Automatic).