SmartServe Kiosk Quality Assurance

Overview

A self-ordering kiosk has no second chance: if a button doesn't respond or an order doesn't save, a customer walks back to the counter. Alongside building the SmartServe self-ordering kiosk for Smart Kiosk, SystemLoom ran quality assurance across the whole system — customer kiosk, admin panel and mobile order page.

The challenge

The kiosk brings several moving parts together: a touchscreen ordering flow, a meal-deal upsell, a cart and checkout, a database of orders, an admin panel and a QR receipt that opens on a phone. Quality assurance had to make sure:

• Every customer journey works, including the less common ones — editing the cart, skipping a deal, starting over.
• The touchscreen feels right: big enough targets, smooth scrolling, no accidental taps.
• Admin changes reach the kiosk correctly — new items, prices, deals and banners.
• Nothing breaks when new features or fixes are released.

What we did

Test cases for every journey

We wrote structured test cases for each part of the flow — welcome screen, category browsing, search, adding items, the "Make it a deal?" prompt, cart edits, checkout, order confirmation and Start new order — including edge cases such as empty searches and removing the last item in the cart.

Touchscreen and kiosk-mode testing

We tested on touchscreens in full-screen kiosk mode, checking tap targets, scrolling, animations and the reset back to the welcome screen between customers.

Admin-to-kiosk checks

For every admin action — adding or editing items, uploading images, creating deals, switching banners — we confirmed the change appears correctly on the kiosk and is saved to the database.

Cross-device testing for the order page

The QR code on each receipt opens an order page on the customer's own phone, so we tested it across different phone sizes and browsers.

Regression testing before release

Before each release we re-ran the core test cases, so a fix in one place doesn't quietly break another.

How testing works

Step	What happens
1. Plan	We list every journey and feature, and write test cases for each
2. Test	We run the cases on touchscreens, desktops and phones
3. Report	Each issue is logged with clear steps to reproduce it
4. Fix & retest	Developers fix the issue and we confirm the fix
5. Regress	Before release, we re-run the core cases end to end

Why choose SystemLoom

Testing works best by the team that knows the product inside out. Because we built the kiosk, our QA covered the real journeys customers and staff use every day — and issues were fixed quickly by the same team.