ecomcloser.com

Shopper holding a top in front of a fitting room mirror

How to test a virtual fitting room before launch

To run virtual fitting room ecommerce QA before launch, test three things separately: whether shoppers can upload or skip a photo, whether the generated preview preserves the garment, and whether shoppers return to the right product and can add the intended variant to the cart. Start with a small acceptance matrix that covers pose, lighting, garment type, silhouette, upload failure and photo deletion. For the visual checks, compare each preview with two real product images, one at a time.

Set a different pass rule for styling and fit. A styling preview can help a shopper imagine a striped shirt with their trousers, but it does not establish that a chosen size will fit across the shoulders. If your store offers measurement-based size guidance, test it separately from the image. Then finish the purchase path: change the colour, try an unavailable size and check the actual cart line. A convincing picture is not a pass if it depicts the wrong garment or sends the shopper back to the wrong variant.

Define what the fitting room is allowed to promise

Start with the wording on the product page, upload screen and result screen. If the feature produces a photo-based styling preview, call it a preview. A button that says See how it looks sets a different expectation from one that says Find your fit. Review the captions and any labels beside the generated image, too. A suitable label at the upload step does not help much if the result itself implies the image is proof of fit.

Give testers three separate verdicts to record. Upload usability covers finding the entry point, selecting a photo, understanding errors and proceeding without a preview. Image fidelity covers whether the output preserves the pose and shows the intended garment with its purchase-relevant details intact. Product and cart continuity covers what happens when the shopper leaves the preview and resumes shopping. One test can pass two of these and fail the third. Do not average the outcomes into one score.

If measurement-based guidance is in scope, give it its own cases. Check, for example, how the guidance handles a measurement near a boundary in the store’s size chart, a missing measurement or a change from centimetres to inches, where those inputs are supported. Record what the guidance actually recommends and compare it with the intended sizing rules. Do not use the shape of a sleeve or the apparent ease of a dress in the generated image as sizing evidence. Keep the size chart easy to reach from the purchase path, even when a preview looks good.

Build a small acceptance matrix

Choose a few actual launch products rather than a collection of images selected because they render well. Start with one patterned garment and one whose shape matters, then vary the photo conditions. Write down what counts as a pass before generating any previews. The examples below are starting cases; replace them with products and capture conditions that match what your store will support on launch day.

Minimum acceptance checks for a virtual fitting room launch
Test case What to inspect Pass condition
Full-body photo in even light Garment placement and body pose. The garment sits in the expected area and the output preserves the submitted pose.
Side angle in low light Capture guidance, output or retry message. The preview is usable, or the shopper gets a specific next step and can continue without it.
Striped shirt Pattern direction, sleeve length and neckline. These features remain recognisable and are not replaced with a different design.
Loose dress Garment identity and silhouette. The correct dress appears and still reads as loose rather than fitted.
Image upload fails Recovery and access to product information. The shopper can retry or continue using real product photos and the size chart.
Shopper clears their photo Visible state and the store’s stated deletion behaviour. The interface reflects the change and the removal or retention matches what the store states.

The side-angle and low-light row combines two stresses to keep the launch matrix small. If it fails, run a well-lit side angle and a dim front-facing photo separately. That tells you whether to improve pose guidance, lighting guidance or both. Make a similar distinction when a loose dress fails: a wrong product is an identity problem, while a correct product rendered with a cinched waist is a silhouette problem.

Add only the cases likely to change your release decision. For example, if long coats are a large part of the launch assortment, test a photo cropped at the knees. Decide in advance whether that photo should be rejected, accepted with a limitation or used for a usable preview. The test should not pass merely because an image came back.

Compare the preview with two real product images separately

Build a review grid with the generated preview beside two real images of the selected product variant. Label each cell with the item and colour. Use a full product view for reference A and a second view or detail image for reference B. The second image should answer a question the first cannot, such as whether the neckline has a stand collar or whether a sleeve ends in a wide cuff. Do not substitute a different colour just because it has a clearer photo.

Reference A: check the garment as a whole

Start with the full view. Confirm that the preview depicts the intended product and colour, then check overall shape, sleeve length and hem placement. For example, a loose A-line dress should not turn into a narrow sheath. Compare the visible contour and construction cues rather than expecting the hem to hit the exact same point on two different bodies. If the preview introduces a belt that the product does not have, record that as an added feature, not a matter of taste.

Reference B: check one detail at a time

Use the second image to score specific features separately. For a striped shirt, compare the neckline, the cuffs and the stripe direction. A preview might look correct from a distance while turning a boat neckline into a V-neck or drawing long sleeves where the product has short ones. If a pose or crop makes a detail impossible to see, mark it not assessable. Do not give credit for a feature you cannot inspect, and do not call an occluded feature missing without evidence.

Keep separate notes for A and B. A preview can pass the overall silhouette comparison and fail the neckline check. Record the actual discrepancy, such as blue shirt; front outline correct; preview replaces button cuff with elastic cuff. Mock previews are illustrative: they can help test labels, layout and navigation, but they do not demonstrate the fidelity of the generated output.

Test capture, waiting and recovery on the intended devices

Run the first upload as a shopper would, from the product page rather than an internal test screen. On mobile, check the available photo-selection routes and what happens when the shopper dismisses the picker. If the experience requests camera access, test denial and confirm that the next step is clear. On larger screens, check that the file control still works without relying on drag and drop. Keep the original product page available to someone who chooses not to share a photo.

Test failures at different points. An unsupported file rejected immediately is not the same as an upload interrupted after a wait, and neither is the same as a completed upload that produces no preview. Check that the message matches what happened. Try a brighter, front-facing photo can help when the capture is the problem; it is misleading when the service cannot complete the request. An actionable error should give the shopper somewhere to go, including back to the real product photos and size chart.

Watch for stale results. For example, start a preview, leave it while it is loading, switch colours and return to the fitting room. If the earlier result appears, it must not look like a preview for the newly selected colour. Try replacing a photo while a result is pending. Check which photo the result is associated with and what happens if the older request finishes later. A loading indicator by itself does not establish that the interface is showing the right request.

Measure the time from photo selection to a usable result and, separately, the time to an actionable error. Note the device and connection conditions. A quick successful run should not hide a failure that leaves a shopper waiting without a retry or exit. Agree on acceptable waiting and recovery behaviour for the launch scope rather than relying on an unexplained average.

Verify photo clearing, deletion and accessible controls

Read the store’s own explanation of photo handling before writing the deletion test. Clearing a photo from the fitting-room screen is not necessarily the same action as deleting a stored upload or a generated preview. Identify what the interface promises to remove, when it says the removal happens and whether the original photo and the output are described separately. Test that stated behaviour; do not infer it from the disappearance of a thumbnail.

After clearing a test photo, reopen the fitting room, reload the page and navigate back if relevant to the experience. Check whether the old image or the associated result reappears. Try clearing while generation is in progress and see whether a late result restores material the shopper expected to remove. Where deletion is promised beyond the visible session, ask the responsible team to verify it through the available system records or documented provider process. If you can only verify that the screen cleared, record that narrower result.

Use WCAG 2.2 as the reference for targeted accessibility checks. Navigate the photo selector, preview controls, retry action, clear action and return path with a keyboard. Check that focus is visible, is not hidden behind another element and goes somewhere sensible when a dialog closes. With a screen reader, confirm that controls have meaningful names and that important progress or error messages can be understood without watching the screen. At a narrow viewport or with enlarged text, check that instructions and exit controls remain reachable.

Keep essential shopping information outside the preview image. The product name, colour, selected size and availability should be understandable without interpreting the generated picture. If a shopper clears their photo, the confirmation should communicate what changed in words rather than relying on a thumbnail vanishing.

Follow the selected variant from preview to cart

Start on a real product page and note the initial colour and size. Preview the item, return to the product page and choose a colour and size there. Check the page state before adding: the controls and product photos should agree about the selection. Then inspect the accepted cart line, not just a success message. Verify the product, variant, colour, size and quantity against what you chose. Where the test view exposes a variant identifier, record it so the team can distinguish a wrong item from a wrong label.

Repeat the flow with a different colour, an unavailable size and a shopper who skips the fitting room entirely. A preview of the first colour must not quietly stand in for the second. An unavailable size should not become purchasable because the shopper reached it from the preview path. The shopper who skips the feature should be able to select a variant and add it without uploading a photo or dismissing the same prompt repeatedly.

If a preview appears to show the wrong colour or garment, trace the reference image back to the selected variant. Check the product page’s image association and, if a product feed is involved, the matching variant and image information there. Google Merchant Center’s product feed specifications are a useful reference for reviewing listings and image fields. A feed check can help explain a mismatched reference; it cannot establish that a generated result faithfully reproduces that reference.

If the flow includes voice selection, score it separately. A spoken colour or size that appears correctly on screen is a selection pass, not an accepted cart action. The cart action passes when the intended line appears in the cart. Payment is a separate checkout outcome and requires its own verification if it is in scope. Neither a spoken acknowledgement nor a correct cart line proves that payment occurred.

Keep demos and workflow descriptions out of the evidence column

A demo can show where a control appears or how a proposed interaction is meant to work. A mock preview can show where reference photos would sit. Neither tells you how the live fitting room handles a side-angle photo, whether it preserves a neckline or what happens when an upload fails. Label illustrative material as such and use results from the actual launch configuration for acceptance decisions.

If you use Senoji BaldinÄ— as a workflow example, keep the owner-described process distinct from facts you can verify in the public product listing. Attribute the description of the workflow to the owner. State only the details you can check directly when discussing the listing itself. A listing is not independent evidence that an interaction was completed, that a cart accepted a line or that checkout took payment. Apply the same standard to your own store: what a shopper can see on a listing and what the system actually did are different kinds of evidence.

Record failures so the team can reproduce them

Give every run a short record: device and browser, product and selected variant, reference images, photo pose and lighting, expected result, observed result and the point at which the issue occurred. Use a test-photo label rather than copying the photo into every issue report. For example, striped shirt, navy, size M; mobile; front-facing photo in even light; preview shortens sleeves; correct variant reaches cart is more useful than try-on looks wrong. It tells reviewers what to inspect and what already passed.

Report counts with meaningful denominators. Count how many upload attempts reach a preview, how many failures offer a usable recovery route, how many assessable previews preserve the required garment details and how many accepted cart actions contain the intended variant. Record unsupported cases and intentionally skipped previews separately. A shopper who chooses to skip the feature has not experienced an upload failure, and an image that loads with the wrong neckline is not a fidelity pass.

Repeat cases where outputs differ between runs. Keep the product, photo and device fixed first so you can see whether the same defect recurs, then change one condition. Note whether the issue follows a specific garment, pose or device. Before adding more categories, check whether the current failures have actionable descriptions and owners. Expanding the assortment before you can explain a wrong preview makes it harder to tell whether a new category introduced a new problem.

Make the release decision by failure type

Set release rules before the last review. Treat a wrong sellable variant in the cart, a blocked path back to shopping or a mismatch with stated photo deletion behaviour as launch blockers for the affected flow. For image fidelity, distinguish details that can change a purchase decision from minor differences in rendering. An invented pocket, a changed neckline or a fitted silhouette on a loose dress can misrepresent the product. A subtle difference in shadow is a different issue if the garment remains recognisable and the preview is clearly labelled.

Limit availability when the evidence supports only part of the intended scope. If the feature works for supported shirts in the tested conditions but repeatedly misrepresents loose dresses, keep it off those dress pages rather than letting one strong result stand in for the category. If side-angle uploads cannot produce useful previews, verify that the capture guidance or retry path gives shoppers a realistic alternative. Re-run the affected cases after any change to the product images, variant mapping or fitting-room flow that could alter their results.

Before signing off, run one final sequence without internal shortcuts: open the live-like product page, upload a supported photo, compare the generated image with both real references, clear the photo, return to the product, select a variant and inspect the cart line. Then do the same shopping task without opening the fitting room. Keep the acceptance matrix with the release notes, including which garments and conditions were tested and which were left out. That gives the next category launch a baseline without implying that untested products have already passed.

Try the EcomCloser demo

Related guides

Sources