d19.112 · Deployment Test Guide

Test the integrated PLENA journey once the full layer is deployed.

This guide exists because the right test is not one page. The right test is the complete buyer journey: homepage, language switch, sector path, builder, evidence packet, verification preview, buyer memo, procurement answers, risk calculator, and mobile layout.

Live browser test sequence

Use real clicks after deployment. Static validation is necessary, but it cannot prove the live browser experience.

Homepage routing

Confirm the homepage shows clear paths for individuals, institutions, ProofOps, buyer room, and market readiness without text overlap.

Open homepage

Language switching

Switch away from English, navigate to at least three pages, return home, and confirm the selected language does not get stuck or reset unexpectedly.

Language integrity

PROVA and ASCENDA

Test PROVA complaint/evidence flows and ASCENDA qualification lookup. These remain live-test priorities and should not be declared fully fixed without browser verification.

PROVAASCENDA

ProofOps builders

Create fictional sample data in the receipt builder, evidence packet builder, verification preview, and export center.

ReceiptEvidence

Buyer path

Open the buyer room, procurement readiness page, risk calculator, sector demo library, and pilot proposal builder.

Buyer RoomRisk

Mobile and console check

Use mobile width, check navigation wrapping, then inspect browser console for uncaught errors.

Site Health

Pass/fail discipline

A page is not considered production-clean merely because the ZIP validation passed. A feature is passed only after it works in the deployed browser, on desktop and mobile, with no serious console errors and no text overlap.

d19.113 · Demo Proof Outputs

PlenaProof now shows the artifacts a pilot can produce.

d19.113 adds fictional sample receipts, a buyer memo, and a pilot packet so the ProofOps demo produces tangible outputs without overclaiming official verification.

Demo outputsSample receipts · buyer memo · pilot packet · demo JSON.Open Demo Outputs →Pilot Packet →
d19.114 · Live QA Console

PlenaProof now has a browser-facing deployment test harness.

Use the Live QA Console after deployment to check critical routes and guide manual testing for language switching, PROVA, ASCENDA, ProofOps builders, buyer room, sample outputs, mobile layout, and console errors.

Test after deploymentRoute checks · manual checklist · language persistence · console review.Open Live QA →
d19.117 · Final Pre-Test Assurance

The integrated PLENA layer is ready for one serious browser test.

Use the final assurance and master test route to verify the whole product after deployment: language switching, PROVA, ASCENDA, ProofOps, Buyer Room, demo outputs, and mobile layout.

Final AssuranceMaster Test Route
d19.119 · Release Candidate Freeze

The integrated build is ready for browser QA.

All named market enhancements are now represented. Pause feature expansion, deploy this candidate, and test the full route map.

Release CandidateBrowser QA Log