KIP Interfaces — Executable Test Plan v0.1.45
Coverage dashboard
16 historical defined test cases. Planned coverage is not evidence of execution. Full requirements-to-tests mapping requires authoritative requirements reconciliation.
| Area | Tests | Planned coverage |
|---|---|---|
| Access control | T-012 | Defined; completeness not yet independently verified |
| Application PHP | T-003 | Defined; completeness not yet independently verified |
| Backlog | T-006 | Defined; completeness not yet independently verified |
| Continuity | T-014 | Defined; completeness not yet independently verified |
| Documentation | T-005, T-008 | Defined; completeness not yet independently verified |
| GitHub | T-013 | Defined; completeness not yet independently verified |
| Release archive | T-010 | Defined; completeness not yet independently verified |
| Release docs | T-015 | Defined; completeness not yet independently verified |
| Release package | T-001, T-002 | Defined; completeness not yet independently verified |
| Release status | T-009 | Defined; completeness not yet independently verified |
| Testing | T-007, T-016 | Defined; completeness not yet independently verified |
| Updater | T-004, T-011 | Defined; completeness not yet independently verified |
Known coverage gaps
- Full Phase 4 unit test suite: NOT YET IMPLEMENTED.
- Complete Phase 5 GitHub write and Phase 6 end-to-end coverage: NOT YET VERIFIED.
- Requirements-to-tests traceability across all historical specifications: INCOMPLETE.
Executable test cases
T-001 — Package integrity
- Type: Automated
- Area: Release package
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Inspect ZIP CRC and safe paths.
- Expected result / pass criterion: ZIP CRC passes; no unsafe paths.
- Result: Open T-001 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-002 — Manifest consistency
- Type: Automated
- Area: Release package
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Run tools/validate-release.py against ZIP.
- Expected result / pass criterion: Manifest hashes and declared version match all files.
- Result: Open T-002 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-003 — PHP syntax
- Type: Automated
- Area: Application PHP
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Run php -l on all packaged PHP files.
- Expected result / pass criterion: Every PHP file parses successfully.
- Result: Open T-003 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-004 — Updater parity
- Type: Automated
- Area: Updater
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Compare nested and sibling updater copies byte-for-byte.
- Expected result / pass criterion: All corresponding updater files match.
- Result: Open T-004 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-005 — Documents navigation
- Type: Manual
- Area: Documentation
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Open every HTML document and follow Back to Documents.
- Expected result / pass criterion: Every link returns to Documents tab.
- Result: Open T-005 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-006 — Backlog dashboard
- Type: Manual
- Area: Backlog
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Compare dashboard counts with backlog register.
- Expected result / pass criterion: Totals reconcile and all gaps disclosed.
- Result: Open T-006 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-007 — Test plan/result linkage
- Type: Automated
- Area: Testing
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Follow every report test ID to plan and return.
- Expected result / pass criterion: All bidirectional links resolve.
- Result: Open T-007 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-008 — Documentation audit
- Type: Manual
- Area: Documentation
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Review HTML audit and machine-readable source.
- Expected result / pass criterion: Findings and counts agree.
- Result: Open T-008 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-009 — Three package references
- Type: Live
- Area: Release status
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Check deployed, latest, accepted URLs and hashes.
- Expected result / pass criterion: Three statuses distinct and no substituted ZIPs.
- Result: Open T-009 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-010 — Immutability
- Type: Live
- Area: Release archive
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Attempt same-version upload with altered ZIP.
- Expected result / pass criterion: Altered package rejected without overwrite.
- Result: Open T-010 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-011 — Backup and restore
- Type: Live
- Area: Updater
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Create backup, simulate failed deployment, restore.
- Expected result / pass criterion: Previously deployed app and data restored.
- Result: Open T-011 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-012 — Authentication
- Type: Live
- Area: Access control
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Access admin while logged out and while admin.
- Expected result / pass criterion: Unauthorized rejected; admin authorized.
- Result: Open T-012 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-013 — GitHub source read
- Type: Live
- Area: GitHub
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Read configured repository file at exact revision.
- Expected result / pass criterion: Correct content and commit SHA returned.
- Result: Open T-013 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-014 — Handoff restart
- Type: Acceptance
- Area: Continuity
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: In fresh session retrieve published handoff and referenced artifacts.
- Expected result / pass criterion: Session identifies authoritative state without prior chat.
- Result: Open T-014 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-015 — Cumulative release notes
- Type: Manual
- Area: Release docs
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Compare release changes against package diff and backlog.
- Expected result / pass criterion: All changes listed; latest released version first.
- Result: Open T-015 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
T-016 — Documentation test coverage
- Type: Manual
- Area: Testing
- Prerequisites: Appropriate local package or authenticated live environment, depending on test type.
- Procedure: Compare every mandatory release requirement to plan test IDs.
- Expected result / pass criterion: Coverage gaps explicitly identified.
- Result: Open T-016 in current test report.
- Requirement mapping: Area-level only; specific backlog ID pending authoritative reconciliation.
CI-CONT-001 — Independent clean-room restart test
Use only final ZIP and accompanying documents to recover requirements, architecture, code/test mapping, unresolved work and reproducible offline commands. Record reviewer, environment, final SHA-256, case-by-case results and explicit PASS/FAIL. See Continuity Verification Matrix. NOT RUN.
Historical release notes and development appendices
Earlier checkpoint descriptions are retained in the versioned Release-Notes-v0.1.41.md through Release-Notes-v0.1.44.md and historical continuity records. They do not describe current v0.1.45 behavior.