Developer reference
Test a PressFlow extension or theme integration
An acceptance matrix for pricing, VAT, checkout, artwork access and production invariants.
Guide source reviewed for PressFlow 1.25.1.
Use a restricted test environment with non-sensitive artwork, controlled mail and a test payment method. This checklist is for an integration you have changed; it is not a claim that every third-party combination has been tested by PressFlow.
Pricing and VAT
| Case | Expected result |
|---|---|
| Valid minimum/reference | Genuine complete-job starting amount and quantity context. |
| Quote-only/no valid reference | Quote/configure label; no nominal price substituted. |
| Change options/copies/dimensions/date | Latest response wins; stale responses do not replace current state. |
| Inclusive/exclusive mode | Same specification's paired amounts switch together, including matrix and unit. |
| AJAX replacement | Saved theme preference applies to new HTML and accessible price labels. |
| Reload with saved preference | Correct visible mode without altering basket/job state. |
| Zero-rated/exempt/location variation | WooCommerce returns appropriate tax amounts; no assumed multiplier. |
| Valid public promotion | Preview and native basket coupon agree without double discount. |
| Expired/removed/conflicting coupon | Eligibility respected; private conditions not advertised universally. |
Repeat meaningful cases in both inclusive-entry and exclusive-entry shops. Do not toggle the entry basis on a production shop solely for testing.
Product template
Test the classic template and the actual builder/block template used by the shop. Confirm one configurator, one intended starting-price slot and one full description below it, or one template-owned content area. Check no nested forms, duplicate IDs or late missing assets. Check unmanaged products retain ordinary WooCommerce rendering.
Basket and checkout
Test classic and block flows where the shop uses both, guest and registered customer, two jobs of the same product with different specifications, inline artwork controls, edit and duplicate. Validate basket quantity one while copies remain inside the job. Change a product price/configuration between basket creation and checkout and confirm the current guard requires a valid job rather than accepting an old browser price.
Artwork and access
Test valid PDF/image, unsupported/oversized file, interrupted upload/retry, combined job limit, transfer link, file expiry and replacement. Test the correct owner, another customer, logged-out account route and valid/expired/revoked guest credentials. Ensure unauthorised preview/download/decisions fail.
Confirm replacement resets relevant review/proof/date decisions. Test stale proof approval and a changed versus unchanged check result. Test manual clearance only against the exact current result. Check production-start locks survive a later hold.
Production, notifications and orders
Try printing with unpaid order, missing/rejected artwork, unresolved check, pending proof and active block flag: each must remain guarded. Test stage progress, explicit hold/resume, planning, public/private notes and dispatch/collection. Verify one dispatched job does not complete a multi-job order.
Inspect queue current/superseded/failed states, disabled email and demo suppression. Retry a current failure after repairing mail, without issuing duplicate offers or proof versions. Check HPOS through CRUD and a queue rebuild on your test data.
Front-end quality
Check keyboard access, focus, selected/disabled states, screen-reader price labels, white text/icons on a suitable accent and mobile overflow. Inspect browser errors and network responses while interacting; a static screenshot alone does not prove behavior.
Record the versions, inputs and expected/actual results. Keep the smallest reproducible fixture when an extension conflict appears.
Related: Hooks, VAT integration, Support diagnostics.
Example files
Reference examples for adapting to your shop. PHP examples are not plugin installers; review the guide and replace sample IDs before using them.
Need a hand?
Contact the PressFlow team with details of what you are trying to do.