78 lines
2.9 KiB
Markdown
78 lines
2.9 KiB
Markdown
# Slice 6: Testing and Release Validation
|
|
|
|
## Status
|
|
|
|
In progress
|
|
|
|
## Objective
|
|
|
|
Produce repeatable automated and manual evidence that the complete MVP builds, runs, and satisfies its acceptance workflows.
|
|
|
|
## Dependencies
|
|
|
|
- Feature-complete Slices 1 through 5
|
|
- Slice 7 release boundary
|
|
- Slice 8 release documentation
|
|
|
|
## In Scope
|
|
|
|
- Toolchain baseline, unit/integration/end-to-end coverage, schema compatibility, production builds, Docker validation, and release evidence
|
|
|
|
## Out of Scope
|
|
|
|
- Post-MVP testing, enterprise load certification, and formal penetration testing
|
|
|
|
## Tasks
|
|
|
|
- [x] Install dependencies from lockfiles and document the supported toolchain.
|
|
- [x] Establish clean frontend and backend validation commands.
|
|
- [ ] Define release-critical coverage and test layers.
|
|
- [ ] Complete frontend component, editor, binding, and Preview tests.
|
|
- [ ] Complete backend CRUD, validation, authentication, proxy, security, and persistence tests.
|
|
- [ ] Add canonical-document persistence round-trip tests.
|
|
- [ ] Add workflow-launcher, dependent-dropdown, and dashboard end-to-end scenarios.
|
|
- [x] Validate all valid and invalid examples.
|
|
- [x] Produce successful frontend and backend production builds.
|
|
- [x] Verify full-stack Docker Compose startup, health, restart, and persistence.
|
|
- [ ] Run the final security regression suite.
|
|
- [ ] Record commands, test counts, artifacts, limitations, and defects.
|
|
- [ ] Update state and the final acceptance checklist.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] A clean checkout can be installed, built, tested, and started from documented commands.
|
|
- [ ] All release-critical automated suites and user workflows pass.
|
|
- [ ] Docker startup, restart, health, and persistence checks pass.
|
|
- [ ] No unresolved critical or high-severity defects remain.
|
|
- [ ] Release evidence and accepted limitations are documented.
|
|
|
|
## Validation
|
|
|
|
- [ ] Frontend checks, tests, and build pass.
|
|
- [ ] Backend checks, tests, and build pass.
|
|
- [ ] Schema matrix and end-to-end suite pass.
|
|
- [ ] Docker integration and security regression checklists pass.
|
|
|
|
## Risks and Open Questions
|
|
|
|
- The first baseline could not run because dependencies were absent.
|
|
- External API tests must use controlled mocks.
|
|
- End-to-end tooling should remain minimal and maintainable.
|
|
|
|
## Progress Log
|
|
|
|
### 2026-07-18
|
|
|
|
- Repaired the frontend lockfile and completed Node 20/npm 10 clean installs.
|
|
- Passed 6 frontend suites with 420 tests.
|
|
- Passed frontend and backend production builds and the schema fixture matrix.
|
|
- Fixed clean-database backend startup ordering.
|
|
- Passed Docker build, startup, health, CRUD, cleanup, and restart persistence.
|
|
- Recorded exact evidence in `BASELINE.md`.
|
|
|
|
## Handoff
|
|
|
|
- Last completed: Initial technical and Docker validation baseline.
|
|
- Next action: Continue release validation as each implementation slice completes.
|
|
- Known blockers: Final validation depends on Slices 1-5; frontend audit findings remain open.
|