forked from longtao.wu/droboticflow
1.8 KiB
1.8 KiB
Test and acceptance matrix
Completion is reported independently for source, automated tests, platform artifacts, browser, POC API, real BOS, signatures, and capacity.
Automated
- Go: API/store/coordinator unit tests, Mongo integration, race detector, status transitions, idempotency replay/mismatch, lease fencing, cleanup, reconcile, quotas, permission gates, and audit chain.
- Rust: format, Clippy with warnings denied, workspace/doc tests, SQLite migrations, deterministic path properties and manifest fuzz corpus, crash/reopen resume, multipart limits, and IPC permission tests. Long-running
cargo-fuzzcampaigns remain a release-certification gate rather than a claim made by routine CI. - React: role visibility, capability gate, pairing approval, conflict, release, audit export, and rollout policy.
- Contract: parse OpenAPI 3.1, regenerate Go/Rust status models, and compare protocol fixtures.
Real BOS
Record request IDs and object evidence for:
- conditional create/update plus HTTP 412;
- direct and multipart staging;
- multipart server-side copy above 5 GB;
- two independent devices creating/updating one key;
- response loss, disconnection, process kill, URL/lease/session expiry, and token revocation;
- external write drift that disables the space;
- traceability among final HEAD/version, session, item, audit, release manifest, and daily seal.
Verify uploads with the drosync receipt and BOS HEAD size/ETag/versionId. A generic object-list entry or UI success badge is not acceptance evidence.
Capacity
Routine CI uses streaming/simulated million-entry manifests and sparse/fixture payloads. Formal certification must preserve the real BOS bill, elapsed time, peak client/server resources, failure/retry log, and final checksum records for 1 million files, one 1 TiB object, and a 20 TiB session.