Tests (QA testing)

The cross-product queue of every QA test prescribed across your setlist — so a maker can run and sign off tests in one place. Passing tests is recommended before launch; required tests also contribute to overall readiness and the dashboard's Needs attention list.

Where: setlist → Tests Tests are created on: each product's detail page Test names come from: Settings → Testing presets

⚠️ "Tests" vs "User testing" — two different features. Tests (this page) = internal QA you run yourself (e.g. a tarnish test, a wear test). User testing = sending physical samples to real people to get feedback. They have similar names but do different jobs.

What it is

The Tests page flattens every test prescribed on every product into a single test queue. Each test is something you need to verify about a product before it's ready — recorded against the product (or a specific option value like "Material: 14k Gold Fill").

You create tests on the product page; you triage and update them here.

How tests fit together

• Define standard tests once in Settings → Testing presets (e.g. "Tarnish / patina test", with a default prescription and a responsible team label).
• Prescribe a test on a product's detail page (Tests section). When presets exist, you pick one from a dropdown and it prefills the prescription + responsible team label (editable). Tests are scoped to an option value where relevant — a test on "Material: Gold Fill" covers every variant with that material.
• Run and sign off here on the Tests page — update each test's status and result, in bulk if you like.

The four overview metrics

Shown only once at least one test exists — an empty queue skips the all-zeros Overview and shows an empty state instead ("No tests in the queue" once you have products, "Start your first test" before that). The page's primary action, Create test, opens the new-product-card form, since tests are prescribed on a product.

Test statuses

Not started · In progress · Passed · Failed · Blocked

The test queue

Columns: Test · Product · Owner · Status · Result. The Product cell links to the product (by its working name) and shows a scope label (e.g. "Material: 14k Gold Fill") for option-scoped tests. Owner is the test's responsible label, not the product's owner. Open tests are listed first; Result reads "—" when empty.

There are no filters or search here — the queue is meant to be worked top to bottom.

Updating tests in bulk

1. Click Bulk edit (top of the Test queue).
2. Each row's Status (dropdown) and Result (text) become editable. A row only joins the draft once you touch it.
3. Click Save — only rows you actually changed get written. Click Cancel to discard.

"Units to test" is set on the product page, not here. Bulk-save persists Status and Result only.

Set it up: step by step

1. (Optional but recommended) Add your standard tests in Settings → Testing presets.
2. On a product's detail page, open the Tests section and Add test (pick a preset or type a name, set the prescription, owner, and units).
3. Come to the Tests page to run them: update each test's status and result as you go (use Bulk edit for many at once).
4. Aim to get tests Passed before launch.

Tips & gotchas

• Required tests affect readiness and attention reporting. Missing or open tests lower the fixed Ready percentage and appear as dashboard blockers. They are not part of the stage Progress gate and do not disable Advance.
• Turn off testing per product if a product doesn't need physical testing (a switch on the product page hides its test sections).
• Scope matters. An option-scoped test ("Size: 7") applies to every variant carrying that value, so you don't re-test each combination.

See also

• Products · The Product Workspace
• User testing — the other testing feature (samples to people)
• Settings → Testing presets