Testing Report — woocommerce

Run ID: 2026-05-06T10-51-02_woocommerce Generated: 2026-05-06T11:43:08.919Z Plugin version: latest Sessions processed: 9 Sessions with errors: 2

Related resources

Document	Link
Cross-charter intelligence (bug patterns, clean areas)	cross-charter-intel.md
Coverage gaps / meta-review	coverage-gaps.md
Feature coverage matrix	coverage.md
Evidence screenshots	evidence-screenshots

Executive summary

Category	Count
Problems	3
Questions	9
Improvements	5
Praises	25

Problem severity breakdown

Severity	Count
critical	0
major	2
minor	1
trivial	0

Severity heatmap by area

Area	Major	Minor	Risk score
Product creation form — Variations tab UI visibility	1	0	3
Virtual + Downloadable product — file attachment, download limits, expiry	1	0	3
External/Affiliate product type	0	1	2
WooCommerce golden path: product creation → discovery → detail → cart	0	0	0
Grouped product type	0	0	0
Product type switching	0	0	0
Bulk edit operations	0	0	0
CSV export/import	0	0	0
Brands taxonomy integration	0	0	0
Category and taxonomy management	0	0	0
shopper-browse	0	0	0
Product detail page — variable product initialization	0	0	0
WP-CLI product variation API	0	0	0
Product detail page — quantity input UX	0	0	0
Product detail page — variable product empty state	0	0	0
Product detail page — form validation	0	0	0
Product detail page — accessibility	0	0	0
Product detail page — consistency	0	0	0
Product duplication	0	0	0
Quick Edit availability	0	0	0
Product data persistence UX	0	0	0
Sale price scheduling	0	0	0
Inventory toggle and stock management	0	0	0
Frontend product display	0	0	0
Product creation form UI behavior	0	0	0
Product type switching interaction	0	0	0
UX / Help text	0	0	0
Variable Product Setup in WooCommerce Admin UI	0	0	0
Price Range Calculation	0	0	0
Linked Products Persistence	0	0	0
Variation Data Integrity	0	0	0
Virtual + Downloadable product form	0	0	0
Virtual checkbox behavior	0	0	0
Downloadable fields persistence	0	0	0
Virtual + Downloadable combination	0	0	0

Risk score = 4·critical + 3·major + 2·minor + 1·trivial

Verification (Phase 5.5)

2 Critical+Major Problem(s) verified — 1 verified ✓ · 1 refuted ✗ · 0 inconclusive ?

Needs human review (confidence < 0.7)

None.

Questions raised

[Bulk edit operations] Does bulk edit on price/stock/status apply only to selected products and preserve unedited fields, or does it clear/overwrite unedited fields?
- Why it matters: Bulk edit is the primary merchant workflow for catalog updates. Silent field clearing would cause data loss on large catalog updates.
[CSV export/import] Does CSV export produce a valid, complete file including all published products? Does import with 'Update existing' mode round-trip without duplicates or data corruption?
- Why it matters: CSV import/export is the primary merchant on boarding path for existing product catalogs. Duplicates or data loss would block store migration.
[Product detail page — variable product initialization] How should a variable product detail page behave when the product is created but has no variations configured?
- Why it matters: The current test environment shows an out-of-stock message without any attribute dropdowns. This may be correct behavior (treating no-variations as out-of-stock) or a configuration issue. Understanding the intended behavior affects whether this is a valid test state or an environment artifact.
[WP-CLI product variation API] What is the correct WP-CLI command syntax for creating product variations with attributes in WooCommerce 10.7.0?
- Why it matters: Multiple WP-CLI variation creation attempts failed: wc attribute create command not found, direct eval with wp_insert_term on pa_color taxonomy failed. Documentation for this workflow in current WC version is unclear.
[Product duplication] Why does the Duplicate row action not produce a visible new product in the product list after clicking and reloading? Is duplication failing silently, or is the duplicate shown in a different view (e.g., drafts tab)?
- Why it matters: H4 hypothesis (deep-copy independence) cannot be empirically tested if duplication doesn't create a product. This is a critical merchant workflow.
[Quick Edit availability] Does WooCommerce 10.7.0 expose Quick Edit for Simple products in the classic product editor, or is Quick Edit only available in the WC Admin dashboard?
- Why it matters: H6 hypothesis depends on Quick Edit being available as a row action. The canonical WordPress Quick Edit pattern may not apply to WooCommerce post types.
[Product creation form UI behavior] Why does the Variations tab appear for all product types instead of being hidden until Variable type is selected?
- Why it matters: Recon S6 stated 'Variations tab is hidden by JS until Variable type selected'. This charter's H1 hypothesis tests this claim. Empirical probing shows the tab is visible for Simple, External, and other types. Is this: (a) a regression where the JS hide logic was removed, (b) an intentional UI change, or (c) a design that WC prefers (show tab always, show message 'add attributes first' for non-variable types)?
[Product type switching interaction] Does changing the product type via the form's type selector (rather than eval) trigger the expected tab hide behavior?
- Why it matters: I changed product type via eval (setting .value and dispatching 'change' event). The page did not visibly update. A click-based user action (selecting from the type dropdown) might trigger a different code path. Requires a fresh test where the UI combobox is clicked and an option is selected via click, not eval.
[Variable Product Setup in WooCommerce Admin UI] When a variable product is created with variations but the parent product's attributes are not explicitly linked via the admin form, why do the variations not display a selector UI on the frontend? Is this expected behavior (variations hidden until attributes are assigned to parent) or a UI gap?
- Why it matters: Wave's previous session failed to probe H5 and H6 because variation selector did not render; clarifying whether this is intentional (attribute assignment required to activate selector) vs. a bug (selector should appear even without parent-level attribute assignment) affects test methodology for variable-product charters.

Suggested improvements

[Product detail page — quantity input UX] Provide clearer visual feedback that the quantity input field is interactive, such as prefilling with the value 1 in a visually focused state. (effort: low) (impact: low)
- Rationale: Users may not immediately recognize the quantity spinbutton as interactive. Current default (1) is correct but could be more discoverable with visual emphasis.
[Product detail page — variable product empty state] Show a more specific message than 'This product is currently out of stock and unavailable' when a variable product has no variations configured (e.g., 'No variations available. Please contact support.'). (effort: low) (impact: medium)
- Rationale: Generic out-of-stock message conflates 'product exists but no stock' with 'product exists but no variants configured'. Distinct messaging helps users understand the situation and take appropriate next steps.
[Product data persistence UX] Display a persistent notification after product save (e.g., 'Product saved at HH:MM') to give merchants immediate visual confirmation rather than requiring them to reload the page. Current behavior requires reload to verify save success. (effort: low) (impact: medium)
- Rationale: Reduces ambiguity for merchants about whether their changes persisted. Improves confidence in form submission patterns.
[UX / Help text] Consider clarifying the Variations tab visibility requirement in product type documentation or the product edit screen (effort: low) (impact: low)
- Rationale: If Variations tab is intentionally visible for all types (with an 'add attributes first' message for non-variable types), this is good UX. If it's meant to be hidden, the current state is confusing. Adding explicit help text to the tab or the product type selector could clarify the expected workflow.
[Virtual + Downloadable product form] Display a more prominent label in the Downloadable files section that indicates at least one file is required. Consider adding an asterisk (*) or 'required' badge next to the 'Downloadable files' heading. (effort: low) (impact: high)
- Rationale: The current help text 'Leave blank for unlimited re-downloads' applies only to the Download limit field, not to the files section. A merchant could misinterpret the label and think the files section is optional.

What works well (praises)

[WooCommerce golden path: product creation → discovery → detail → cart] End-to-end product value chain is fully functional and data-faithful. Merchant publishes simple product with title, price, and description; shopper discovers it on /shop/ with correct title and price; detail page shows all data faithfully; add-to-cart succeeds and cart reflects exact product state.
- Why: This is the core WooCommerce experience. Every merchant and shopper relies on this chain working correctly. The fact that title, price, and description persist end-to-end without corruption, and that the cart reflects the correct totals, is a critical quality baseline met.
[Grouped product type] Grouped product field visibility correctly changes based on product type selection; child product linking via grouped_products meta persists correctly; frontend rendering displays each child product with individual price, quantity, and add-to-cart button
- Why: Complex product types like Grouped depend on correct form field visibility and data persistence. Merchants bundling products expect child products to render correctly on the frontend with individual add-to-cart controls, which this implementation delivers.
[External/Affiliate product type] External product type correctly replaces price fields with Product URL and Button text fields; external_url and button_text meta values persist on save; frontend button renders with custom text and navigates to the external URL when clicked
- Why: Affiliate merchants need a reliable way to link to external products with custom button labels. The External product type correctly handles the metadata persistence and frontend rendering, enabling affiliate storefronts.
[Product type switching] Type selector combobox reliably changes visible form fields; switching from Simple to Grouped removes price fields and shows child product picker; switching to External shows URL and button text fields instead of prices
- Why: Merchants need confidence that switching product types in the form dynamically updates the visible fields to match the selected type's data model. This feature enables flexible product management workflows.
[Brands taxonomy integration] Brands (new in WC 10.x) is fully integrated into the product edit screen and has a dedicated archive URL structure (/brand/slug/) that works end-to-end.
- Why: New taxonomy feature that could have had registration or permalink issues; it's clean and follows WooCommerce patterns seamlessly.
[Category and taxonomy management] Category and brand creation UI is consistent with WordPress taxonomy conventions. Forms are clear, fields are well-labeled, success feedback is immediate.
- Why: Consistent UX reduces merchant confusion and supports self-service catalog setup.
[shopper-browse] Out-of-stock products correctly show status instead of Add to cart button
- Why: Out-of-stock Delta Product displays 'Out of stock' status on both /shop/ product card and detail page, with no 'Add to cart' button present, preventing guest confusion about whether a product can be purchased.
[shopper-browse] Sale price badge with original and discounted price renders consistently across surfaces
- Why: Gamma Product displays 'PRODUCT ON SALE' (or 'Sale!') badge with both original ($25) and current sale ($15) prices on /shop/ grid and detail page with strikethrough on original price, ensuring consistent display across product browsing surfaces.
[shopper-browse] Price sorting (low-to-high, high-to-low) works correctly with numeric comparison
- Why: Sort dropdown applies correct numeric ordering in both directions (Low-to-high: $5 → $10 → $15 → $50; High-to-low reverses correctly), avoiding common string-comparison bugs where $10 would sort before $9.
[shopper-browse] Product search recall returns correct product and handles empty results with clear messaging
- Why: Search for 'Alpha' returns Alpha Product in results, and searching for nonsense term shows 'Sorry, but nothing was found' message instead of blank page, providing clear user feedback.
[shopper-browse] Category archive correctly filters products by assigned taxonomy
- Why: Featured category shows only Alpha Product (assigned via CLI) with page displaying 'Showing the single result', and other products correctly absent, demonstrating taxonomy query filter is working.
[shopper-browse] Empty-state rendering for zero products displays 'No results found' with proper page layout
- Why: When all products are deleted, /shop/ displays 'No results found' message with layout remaining intact (not blank page), ensuring clear user communication when no products exist.
[shopper-browse] Product visibility parity between guest and logged-in customer
- Why: Logged-in customer sees same 4-product grid on /shop/ as guest with no role-gated product hiding, ensuring consistent catalog visibility across authentication states.
[Product detail page — form validation] Quantity input validation correctly rejects invalid values (0) with a clear, specific error message.
- Why: The error message 'Value must be greater than or equal to 1' provides excellent user feedback and prevents invalid cart additions. Users are not confused about why the action failed.
[Product detail page — accessibility] Quantity input is properly labeled for accessibility and Add to cart button is semantic HTML button element.
- Why: Both elements are fully keyboard-navigable and screen-reader compatible. The label text 'Detail Test Simple quantity' and semantic button markup ensure users with assistive technology can discover and interact with these controls.
[Product detail page — consistency] Product detail page renders identically for both guest and authenticated customer users.
- Why: Consistent experience regardless of login status ensures shoppers have the same product information and purchasing ability whether or not they have an account.
[Sale price scheduling] Sale price date fields (date_on_sale_from, date_on_sale_to) persist correctly across save/reload cycles and render the sale badge on the frontend when the current date falls within the scheduled range.
- Why: Date-based conditional features are historically bug-prone (timezone handling, leap year boundaries, DST transitions). This feature works reliably and the frontend correctly evaluates the date condition on every load.
[Inventory toggle and stock management] The 'Manage stock' toggle correctly shows/hides inventory-related fields (stock quantity, stock status) and persists the checkbox state across save/reload. Toggling the checkbox also properly enables the stock quantity input field.
- Why: This is a JS-driven show/hide pattern which often fails to persist state due to non-idempotent save handlers. WooCommerce handles this correctly.
[Frontend product display] After creating and publishing a Simple product with price, title, and sale price, the product immediately appears on /shop/ and /product// with correct pricing (sale price shown with strikethrough regular price). No cache flush or admin action required.
- Why: Frontend visibility after save is a critical merchant expectation. Instant visibility without workarounds indicates clean data flow from post creation through frontend template rendering.
[Price Range Calculation] Frontend product page correctly calculates and displays min/max price across all variations ($10–$25 range) without manual merchant input
- Why: Automatic range display reduces merchant configuration errors and provides transparent pricing to customers at a glance
[Linked Products Persistence] Upsell and cross-sell product assignments persist correctly via WC CRUD API and render in 'You may also like…' section on product detail
- Why: Reliable persistence of merchant-set associations is critical for e-commerce recommendation flows; confirmed round-trip from admin to customer-facing display
[Variation Data Integrity] Multiple variations (4 created; 2×2 Cartesian) with distinct SKU and price values all persist and are retrievable via WP-CLI with full fidelity
- Why: Data integrity across variations is fundamental to variable product feature; no corruption observed even with concurrent variation creation
[Virtual checkbox behavior] Virtual checkbox immediately hides the Shipping tab from the Product data meta box when checked, and immediately re-shows it when unchecked
- Why: This is excellent UX — it immediately communicates to merchants that Virtual products don't require shipping configuration, without requiring a page reload or confirmation dialog
[Downloadable fields persistence] All three downloadable-product fields (file URL, download limit, download expiry) persist correctly through save-and-reload cycles and are stored with proper meta keys
- Why: This is critical functionality that works correctly — merchants can rely on their download configurations being preserved
[Virtual + Downloadable combination] Virtual and Downloadable can be used together on the same product without conflict or hidden fields
- Why: This enables the legitimate use case of virtual, downloadable products (e.g., e-books, digital guides). The two checkboxes are truly independent.

Coverage gaps

Session	Status	Turns	Flows	Notes
`golden-path-product`	complete	25/25	4/4	All four golden-path hypotheses (GP1–GP4) were empirically probed and confirmed passing. Merchant created a Simple product with title, price ($49.99), and description; published successfully with confirmation notice. Shopper navigated to /shop/ and found the product with correct title and price on the card. Shopper viewed detail page and verified all merchant-entered data rendered faithfully (title, price, description). Shopper added product to cart and verified cart page showed correct product name, unit price ($49.99), quantity (1), and line total ($49.99). No blocking errors, no data corruption, no UI failures observed. Empty-price validation probe deferred due to budget (not executed). Featured image was not added to the product (optional for this golden-path probe); all other merchant data was complete.
`product-catalog-admin`	complete	22/22	4/7	Charter theme: product catalog management (categories, tags, Brands, bulk edit, CSV import/export). Executed Flows 1-4 with focus on SFDPOT dimensions (Function, Data, Operations) per charter sampling strategy (balanced). H1 (Brands taxonomy) PROBED and PASSED — brand creation, assignment, and frontend archive page all work end-to-end. H2 (category archive routing) PROBED PARTIALLY — two categories created successfully; category archive page renders correctly at /product-category/category-1/. H3-H6 (bulk edit, CSV export/import) DEFERRED due to turn budget limit. Empty-state probe (Flow 7) not executed. Turns remaining: 0.
`shopper-product-detail`	complete	13/22	4/6	Successfully tested simple product detail page (H1: PASS) and quantity input validation (H5: PASS). Tested variable product out-of-stock display (H3: partial). Unable to fully probe H2 (price update on variation select) and H4 (missing attribute validation) due to variable product lacking configured variations in test environment. WP-CLI variation creation via eval failed due to attribute taxonomy not being registered. Tested as both guest and logged-in customer personas. Accessibility baseline verified (quantity label present, button properly marked). Recon confirmed simple product created; variable product created but uninitialized with variations.
`simple-product-merchant`	complete	24/25	6/8	Completed core product creation and persistence flows (Flows 1-4, 6). Verified that manage_stock toggle, inventory quantity, sale price, and date range fields all round-trip correctly through save/reload cycle. Verified product appears on shop frontend with correct pricing (sale price shown). Intentionally deprioritized: duplication independence probe (H4), trash/delete flow (H5), quick edit (H6), linked products (H7), and empty-state probe (Flow 8). Budget exhausted at turn 24 of 25; remaining flows required more than 1 turn each.
`variable-product-merchant`	complete	24/25	3/6	Explored product creation flow with focus on H1 (Variations tab visibility). Discovered Variations tab IS visible on new product form for all product types, contradicting recon S6 claim. Product type selector is hidden by default but becomes accessible via eval/JS. Attribute save/persistence workflow needs further probing in subsequent sessions. H4-H6 flows not executed due to turn budget constraints (turn 24/25 used).
`variable-products-supplementary`	complete	22/25	5/6	H3 (generate variations + persist): PROBED via CLI. H4 (per-variation price/SKU persist + range display): PROBED via CLI state verification + frontend screenshot showing $10–$25 range. H7 (upsells/cross-sells persist + render): PROBED via CLI + frontend verification of 'You may also like…' section. H5 (out-of-stock unavailability) and H6 (validation on attribute selection) deferred because product attributes were not linked to the parent product via the admin UI—variations exist but the variation selector never renders on the frontend without this linkage. Empty-state probe (H6 variant: generate 0 variations) deprioritized due to budget. Merchant outcome checklist item 'For variable products: every published variation shows the correct price' partially verified (price range correct, individual variation prices confirmed via CLI), but attribute-selection interaction left un-probed on customer-facing side.
`virtual-downloadable-merchant`	complete	15/20	4/5	H1 (Virtual checkbox removes Shipping tab) fully probed. H2 (downloadable fields persist) fully probed and verified with CLI. H3 (Virtual + Downloadable together) fully probed. H4 (empty file validation and unlimited limit) partially probed — empty file validation completed (FAIL case found); unlimited-limit display verification was blocked by server timeout but data was verified via CLI. Flow 5 (H4 unlimited sentinel) deprioritized due to turn budget and server issues — WooCommerce stores -1 as the unlimited sentinel, and this is not displayed to users by default (the help text says 'leave blank for unlimited'); no specific problem found with the -1 sentinel handling.

Environment warnings

These are signals observed during the run that point at test-environment quirks (Studio + SQLite shim, WP-CLI Phar, WC stack interactions), NOT plugin defects. Apply extra scrutiny to findings in affected areas — some Problems may be false positives caused by the environment, and some real bugs may be masked.

Session	Warning
`golden-path-product`	Studio language-pack loader failed during setup (ENOENT on /Users/alopezari/.studio/server-files/language-packs/id_ID-*.json); does not affect plugin testing or WooCommerce functionality.
`simple-product-merchant`	WooCommerce was not pre-installed by studio-provision.sh despite being the target plugin and manifest indicating ecosystem='woocommerce'. Manual installation via 'studio wp plugin install woocommerce --activate' was required. This suggests provision script logic may not account for the case where the target plugin is WooCommerce itself.
`simple-product-merchant`	Product duplication behavior differs from standard WordPress post duplicator. The row action exists and is clickable, but the duplicated product does not appear in the product list after the action completes. Duplication may succeed silently or redirect to a different view. This requires investigation to determine if the behavior is intentional or a defect in the WooCommerce duplication handler.
`virtual-downloadable-merchant`	Server became unresponsive (navigation timeouts) after turn 15 on edit.php and product edit pages; admin home /wp-admin/ also timed out. Likely a Studio / SQLite transient issue, not a plugin defect. WP-CLI remained responsive throughout, allowing data verification via CLI commands.
`virtual-downloadable-merchant`	WooCommerce 10.7.0 was installed during the session after initial provisioning showed 'Invalid post type' error. The provisioning script did not install WooCommerce automatically despite the run's target being 'woocommerce' plugin — this suggests the provisioning process may not have detected the target plugin correctly.

Invalid / failed session reports

`recon`

No report.json produced

`verifier`

No report.json produced

Token usage & cost

Computed from Claude Code transcripts at ~/.claude/projects/<proj-hash>/. Rates from config/pricing.json. Window: 2026-05-06T10:51:02Z → 2026-05-06T11:24:43Z (with ±10min buffer for dispatch drift).

Estimated total cost for this run: $22.73

Category	Cost	% of total
Fresh input	$0.00	0.0%
Output	$2.41	10.6%
Cache-create (5m)	$3.99	17.5%
Cache-create (1h)	$1.93	8.5%
Cache-read	$14.40	63.4%

Manager (main conversation)

Total: $5.78

Model	Messages	Input	Output	Cache-5m	Cache-1h	Cache-read	Cost
`claude-sonnet-4-6`	93	124	64,326	0	322,040	9,607,815	$5.78

Subagents (10 invocations)

Total: $16.95

Model	Messages	Input	Output	Cache-5m	Cache-1h	Cache-read	Cost
`claude-haiku-4-5-20251001`	1351	1,582	152,726	1,542,417	0	90,281,295	$11.72
`claude-sonnet-4-6`	132	144	45,370	548,713	0	8,292,841	$5.23

Per-subagent breakdown (10 sessions)

Agent ID	Type	Models	Cost
`a142b500986a0fd7b`	tester	claude-haiku-4-5-20251001	$1.15
`a3d9e8a93587b6d92`	tester	claude-haiku-4-5-20251001	$1.77
`a452c4fdb7a02f9d8`	tester	claude-haiku-4-5-20251001	$1.57
`a5565790937524971`	tester	claude-haiku-4-5-20251001	$1.92
`a5d8f3b26917c33b0`	tester	claude-haiku-4-5-20251001	$1.86
`a6829f3a956354e6c`	planner	claude-sonnet-4-6	$2.29
`a818ce9938cfc0a19`	tester	claude-haiku-4-5-20251001	$1.09
`af1811a4415c4e367`	tester	claude-haiku-4-5-20251001	$1.33
`af1ee3439225933c1`	tester	claude-haiku-4-5-20251001	$1.04
`af74c0710afb1a9f3`	tester	claude-sonnet-4-6	$2.94

Recommended next steps

Triage Product creation form — Variations tab UI visibility first — highest risk score (3)
Follow up on 7 session(s) with incomplete coverage
Investigate 2 session(s) that failed to produce valid reports

alopezari/final-report.md Secret

Select an option

No results found