Test-case specification
Cases are organized by the verification boundary they exercise. System tests exercise the integrated tool through Sphinx, the browser or package installation. Software tests exercise individual implementation components. Classify by the procedure, not merely by the prefixes of linked requirements: one system test may also provide evidence for software requirements without being duplicated.
Canonical IDs, requirement links, latest results and historical execution records are retained. A folder move does not imply a new run or acceptance. Software unit scripts live with their owning components; integrated system scripts remain under Executable test scripts.
- System test cases
- STV_TC_SY_001: usability smoke
- STV_TC_SY_002: control order smoke
- STV_TC_SY_003: missing placeholder and detail error
- STV_TC_SY_004: failed finalization retains pending page and previous assets
- STV_TC_SY_005: seed layout replacement failure and staleness
- STV_TC_SY_006: alternate host schema external metadata and parts
- STV_TC_SY_007: documentation visuals
- STV_TC_SY_008: invalid seed source location
- STV_TC_SY_009: control order smoke
- STV_TC_SY_010: interactive seed smoke
- STV_TC_SY_011: seed capacity at directive
- STV_TC_SY_012: missing placeholder and detail error
- STV_TC_SY_013: cross page bundle
- STV_TC_SY_014: invalid seed source location
- STV_TC_SY_015: alternate model geometry details and external
- STV_TC_SY_016: usability smoke
- STV_TC_SY_017: large project at visible capacity
- STV_TC_SY_018: invalid mapping has entry path and location
- STV_TC_SY_019: seed selection release
- STV_TC_SY_020: async layout failure and stale completion
- STV_TC_SY_021: interactive seed smoke
- STV_TC_SY_022: invalid seed source location
- STV_TC_SY_023: seed capacity at directive
- STV_TC_SY_024: prior fatal exception is not replaced by bundle generation
- STV_TC_SY_025: project paging
- STV_TC_SY_026: incremental body change hidden and deleted objects
- STV_TC_SY_027: host owns broken trace failure
- STV_TC_SY_028: seed selection release
- STV_TC_SY_029: host default directional labels are used
- STV_TC_SY_030: offline exploration
- STV_TC_SY_031: project paging
- STV_TC_SY_032: async layout failure and stale completion
- STV_TC_SY_033: alternate model geometry details and external
- STV_TC_SY_034: empty seed catalog
- STV_TC_SY_035: large project at visible capacity
- STV_TC_SY_036: seed layout replacement failure and staleness
- STV_TC_SY_037: offline exploration
- STV_TC_SY_038: clean wheel host
- STV_TC_SY_039: empty seed catalog
- STV_TC_SY_040: unsupported builder fails clearly
- STV_TC_SY_041: Select separate occurrences
- STV_TC_SY_042: Restore occurrence exploration
- STV_TC_SY_043: Isolate occurrence expansion
- STV_TC_SY_044: Merge shared expansion sets
- STV_TC_SY_045: Inspect details from a nested Windows checkout
- STV_TC_SY_046: Reject unaudited distribution inputs
- STV_TC_SY_047: Authored transport markers remain inert over file
- STV_TC_SY_048: Authored transport markers remain inert over HTTP
- STV_TC_SY_049: Retained historical archives carry a complete licensing supplement
- STV_TC_SY_050: Patched offline distribution remains usable on Python 3.10
- STV_TC_SY_051: Actual source archive respects the distribution boundary
- STV_TC_SY_052: Clean rebuild retires obsolete publication files
- STV_TC_SY_053: Failed documentation build preserves published bytes
- STV_TC_SY_054: Failed directory promotion restores previous publication
- STV_TC_SY_055: CI policy rejects privilege and provenance drift
- STV_TC_SY_056: Candidate checksums detect changed artifact bytes
- STV_TC_SY_057: CI runtime command imports the installed Python 3.10 package
- STV_TC_SY_058: Stable keyboard navigation and project root toggles
- STV_TC_SY_059: Negative route rendering and viewport reset
- STV_TC_SY_060: Natural seeded order survives expansion
- STV_TC_SY_061: Published nine-row evidence navigation
- STV_TC_SY_062: Visible viewport boundary during graph navigation
- STV_TC_SY_063: Persistent details across navigation and capacity
- STV_TC_SY_064: Persistent loading cancellation and shared content safety
- STV_TC_SY_065: Readable details, metadata disclosure and artifact-ID navigation
- Software test cases
- STV_TC_SW_001: reverse traversal has no depth cutoff
- STV_TC_SW_002: parent and project center over five visible children
- STV_TC_SW_003: page boundaries, root capacity and independent views
- STV_TC_SW_004: semantic bands and shared test lane
- STV_TC_SW_005: external original url rejects executable or nonportable navigation
- STV_TC_SW_006: self-loop terminates and collapse restores the only seed
- STV_TC_SW_007: replacement level mappings drive ordering without relation-name assumptions
- STV_TC_SW_008: runtime reseeding is atomic and clears exploration
- STV_TC_SW_009: host normalization
- STV_TC_SW_010: clear facing ports and fan-in avoid outer detours
- STV_TC_SW_011: competing parents do not displace a separate centered parent
- STV_TC_SW_012: project pages preserve independent expansion and collapsed root
- STV_TC_SW_013: invalid directional labels
- STV_TC_SW_014: classic registration treats prototype keys and script text as data
- STV_TC_SW_015: rooted diamond and isolated cycle
- STV_TC_SW_016: invalid model
- STV_TC_SW_017: invalid model
- STV_TC_SW_018: 199/200/201 atomic capacity
- STV_TC_SW_019: external original url rejects executable or nonportable navigation
- STV_TC_SW_020: external original url rejects executable or nonportable navigation
- STV_TC_SW_021: portable paths preserve queries and fragments
- STV_TC_SW_022: shared children keep unique nodes and conflicting parents do not overlap
- STV_TC_SW_023: invalid directional labels
- STV_TC_SW_024: blocked skipped-level edges retain safe detours
- STV_TC_SW_025: srcset data images and css resources
- STV_TC_SW_026: cross-page targets do not acquire synthetic root edges
- STV_TC_SW_027: upward controls precede neutral and downward controls regardless of authorship
- STV_TC_SW_028: invalid model
- STV_TC_SW_029: hidden parts external and missing targets
- STV_TC_SW_030: cyclic shared geometry with isolated nodes remains deterministic and separated
- STV_TC_SW_031: invalid directional labels
- STV_TC_SW_032: static details and remote fallback
- STV_TC_SW_033: Concurrent build-scoped detail loading
- STV_TC_SW_034: Retry local detail loading after failure
- STV_TC_SW_035: active embed urls are not retained as navigation
- STV_TC_SW_036: local suggestions match IDs and titles and bound results
- STV_TC_SW_037: invalid directional labels
- STV_TC_SW_038: invalid model
- STV_TC_SW_039: Compact immutable detail assets
- STV_TC_SW_040: Reserved authored transport attributes are discarded
- STV_TC_SW_041: Restored URLs obey the output-local policy
- STV_TC_SW_042: Restored CSS rejects unchecked resources
- STV_TC_SW_043: Stable navigation geometry and boundary cases
- STV_TC_SW_044: Complete finite SVG bounds
- STV_TC_SW_045: Natural ID ordering for fresh scenes
- STV_TC_SW_046: Validate classified placement configuration
- STV_TC_SW_047: Resolve stable classification and fallback records
- STV_TC_SW_048: Align classified rows through navigation
- STV_TC_SW_049: Ordered detail collection capacity and reuse
- STV_TC_SW_050: Persistent limit configuration validation
Numeric case identity
Canonical test cases use independent category sequences:
System cases:
STV_TC_SY_001onward.Software cases:
STV_TC_SW_001onward.
Allocate the next unused number within the case’s verification category; never recycle numbers or renumber cases merely for sorting or moving a document. A change of verification category requires an explicit mapped ID migration.
The owner authorized replacing the hash/descriptive IDs on 2026-10-24, then refined the convention to category prefixes and separate counters. All 99 cases and live RST references were migrated. Procedures, selectors, requirement links, statuses, results and execution IDs are unchanged. Numbers follow existing order within each category. This editorial migration implies no new execution, acceptance or release qualification. The map retains both original IDs and the intermediate project-wide numeric IDs.
Original logs, XML/CSV/JSON reports, archived source/artifacts and historical content hashes retain their original bytes and IDs. Use the mapping to resolve those historical IDs to current cases; earlier review hashes continue to identify the original revisions. Current rendered execution references use the new IDs.