v0.2.0-dev — Complete Testing Plan + Build Pipeline Verification #11
Labels
No labels
meeting-notes
meeting-sensitive
meeting-transcript
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coopcloud_code/home#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Complete Testing Plan for Marketplace
Before calling anything production-ready, we need a solid testing foundation. Following the freezone pattern (znzfreezone_code/home#15).
The platform currently has unit tests and manual make targets — no automated E2E, no smoke automation, no browser tests.
Step 1: Build Pipeline Verification
Problem: Container builds hit multiple issues during v0.1.0-dev (Podman image names, missing directories, Rust version, Dioxus output paths, binary names). All fixed but need a clean end-to-end verification.
Fix: Fresh clone →
make dist TAG=0.2.0-dev→ all 3 images build without errors.make forge-release TAG=0.2.0-devcreates Forgejo releaseStep 2: Smoke Tests (curl-based, all endpoints)
Script:
tests/smoke.sh— runs against any base URL (local or live).Runs: locally after containers start, and against live endpoints.
Step 3: API Integration Tests (demo/fixtures mode)
Script:
tests/api_integration.sh— exercises the full RPC API.Runs: against backend in fixtures mode (no external services needed).
Step 4: Playwright E2E Browser Tests
Config:
tests/playwright/playwright.config.ts4a. Marketplace Browse (
marketplace.spec.ts)4b. Cart + Checkout (
cart.spec.ts)4c. User Registration + Login (
auth.spec.ts)4d. Dashboard (
dashboard.spec.ts)4e. Wallet (
wallet.spec.ts)4f. Node Management (
nodes.spec.ts)4g. Service Provider (
services.spec.ts)4h. Messaging (
messaging.spec.ts)4i. Node/Slice Rental (
rental.spec.ts)4j. Admin Dashboard (
admin.spec.ts)4k. Marketing Website (
website.spec.ts)4l. SEO Pages — SSR (
seo.spec.ts)Step 5: Unit Test Expansion (cargo test)
Add to existing tests in backend:
Step 6: White-Label Verification Tests
Step 7: CI Integration
Update
.forgejo/workflows/build.yamlin each repo:File Structure
Coverage Summary
Not Covered (requires real providers or infrastructure)
These are manual/staging tests, not automatable without provider sandboxes.
Implementation Order
All tests must pass before v1.0.0 release.
Reference: znzfreezone_code/home#15
Progress update (2026-03-24)
Build pipeline verified:
Automated SPA smoke test developed (browser-based):
Test harness runs in hero_browser MCP — could be formalized into a reusable script.
Remaining for this issue:
tests/smoke.shSigned-off-by: mik-tf
Closing — testing plan implemented (2026-03-24)
Automated SPA smoke test:
tests/smoke.shBuild pipeline verified:
Usage:
Remaining (future issues):
Signed-off-by: mik-tf