The Project
- Select from a list of curated phones
- Choose a recipient for the phone
- Choose the address where the phone should be sent
- Enable customers to view the phones they have ordered
- Set up the flow so that, when an order is placed, it is automatically created as a task in Asana
- Configure order confirmation emails for both admins and users
Potential Extra Features
- Should customers be able to cancel orders?
1. Objective
The goal of this test plan is to validate the functionality, usability, and reliability of the new webshop feature that allows clients to select and purchase mobile phones from a web-based interface. This includes front-end interaction, data flow to admin interfaces, dynamic visual updates, and notification systems.2. Scope of Testing
The test scope includes:- Product display and selection on the webshop (UI)
- Variant selection (color + storage) via dropdown
- Conditional image rendering based on selected variant
- Add to cart functionality
- Purchase confirmation logic and email notifications
- Order visibility and accuracy in the admin panel
- Currency display based on customer HQ location
- Price validation based on partner data (Mutonic)
- Full order tracking (“Processing”, “Shipped”, etc.)
- Cancel order functionality
- Payment integration (if applicable, may be added later)
3. Test Areas & Approach
3.1 Product Catalog Validation- Ensure all defined models, colors, and storage combinations are present
- Check dynamic dropdown content per product card
- Confirm accurate mapping between UI and backend model list
- Verify all combinations appear correctly
- Ensure each selection triggers correct image rendering
- Changing the dropdown value must change the product image
- Each image must match its selected color
- Items can be added to cart with selected configuration
- Items are preserved correctly in the cart view
- Correct pricing is displayed per item
- Admin must be able to view orders associated with users
- Orders should show model, color, storage, and timestamp
- One email sent to user confirming order
- One email sent to admin that order was placed
- Ensure currency displayed based on user’s HQ
- Validate fallback behavior
4. Test Types
Functional Testing – Test core workflows (selection, ordering, admin sync) UI Testing – Visual checks for image rendering, dropdown display Integration Testing – Ensure backend syncs correctly with UI and admin Regression Testing – Ensure existing features are unaffected Email Testing – Verify correct template, data, and triggers Localization Testing – Currency/format checks based on user location5. Test Data Requirements
- Full model list with all variants
- Sample user accounts (HQ: DE, US, etc.)
- Admin account access
- Mutonic pricing structure
- Sample email inboxes (for notification testing)
6. Environment Requirements
- Staging environment mirroring production
- Access to Swagger/Postman for backend validation
- Figma image assets hosted and referenced correctly
- Email service (HubSpot) enabled in staging
7. Risks & Mitigations
Missing variant images – Users see incorrect visuals – Fallback images + asset completeness check Incorrect prices – Mismatch with Mutonic – Manual spot checks + automation validation Email not sent – Broken notification flow – Monitor logs, set fallback retry Wrong currency shown – Misleading pricing – Add QA cases per location & test fallback8. Tools & Resources
- Swagger / Postman — for API testing
- Figma — source of image assets
- Mintlify — documentation reference
- qa.tech — for automated test cases (future phase)
9. Exit Criteria
- All high- and medium-priority test cases passed
- No open critical bugs
- Manual and automated test reports
- Approval from product owner and tech lead