# INVEETAIRE

# ALPHA ACCEPTANCE TEST (AAT-001)

You are acting as the Lead QA Engineer for the INVEETAIRE platform.

This is NOT an implementation task.

Do NOT modify code.

Do NOT create files.

Do NOT refactor architecture.

Do NOT suggest future features.

Your only responsibility is to perform a complete Alpha Acceptance Test.

---

# Current Status

Sprint 0
COMPLETE

Sprint 1
COMPLETE

Sprint 2
COMPLETE

Sprint 3
COMPLETE

Pilot-001
COMPLETE

Pilot-002
COMPLETE

Pilot-003
COMPLETE

Pilot-004
COMPLETE

Pilot-005
COMPLETE

Pilot-006
COMPLETE

Pilot-007
COMPLETE

Alpha Patch-001
COMPLETE

Current Repository Status

ALPHA BASELINE

---

# Objective

Validate that the entire platform is ready for one real wedding.

Assume the system will be used by:

* Couple
* Crew
* Wedding Guests

Do NOT review architecture.

Do NOT review code quality.

Test ONLY business workflows.

---

# Test Environment

Create one workspace.

Workspace slug:

test-couple

Use realistic wedding data.

Create at least:

30 guests.

Include:

Holy only guests

Reception only guests

Holy + Reception guests

VIP guests

Family

Friends

Vendors

Guests without phone numbers

Guests with duplicate names

Guests with different invited pax

---

# Acceptance Test Flow

Execute every workflow.

---

## 1. Workspace

Verify:

Workspace creation

Workspace provisioning

Default configurations

Publication

Expected:

PASS / FAIL

---

## 2. Invitation

Verify:

Bride

Groom

Love Story

Wedding Date

Venue

Gallery

Gift

Countdown

Theme

Preview

Publish

Expected:

PASS / FAIL

---

## 3. Guest Import

Verify:

CSV

XLSX

Duplicate detection

Guest code generation

Guest groups

Guest categories

Seat numbers

Invited pax

Expected:

PASS / FAIL

---

## 4. Public Invitation

Verify:

Correct guest

Correct greeting

Correct event assignment

Holy only

Reception only

Dual events

QR rendering

404 handling

Expected:

PASS / FAIL

---

## 5. Guest Interaction

Verify:

RSVP

Update RSVP

Wish

Update Wish

Invalid token

Expected:

PASS / FAIL

---

## 6. Messaging

Verify:

Template

Placeholder replacement

Preview

Copy Message

Copy Link

WhatsApp button

Guest without phone

Expected:

PASS / FAIL

---

## 7. Wedding Operations

Verify:

Scanner

Invalid QR

Guest resolution

Check-In

Repeated scan

Dashboard

Statistics

Expected:

PASS / FAIL

---

## 8. Security

Verify:

Workspace isolation

Draft invitation

Inactive workspace

Invalid guest token

Malformed token

Unauthorized crew page

Unauthorized couple page

Expected:

PASS / FAIL

---

## 9. User Experience

Review:

Navigation

Error messages

Validation

Loading flow

Button clarity

Mobile friendliness

Crew workflow

Couple workflow

Guest workflow

Classify:

Excellent

Good

Needs Improvement

---

# Bug Classification

Every issue must be classified.

Critical

High

Medium

Low

Cosmetic

Only Critical blocks Alpha.

---

# Deliverables

Produce:

1. Executive Summary

2. Acceptance Test Matrix

3. Failed Test Cases

4. UX Findings

5. Security Findings

6. Reliability Findings

7. Bug List

8. Severity Classification

9. Alpha Readiness Score (0–100)

10. Final Decision

Choose ONLY one:

APPROVED FOR ALPHA

or

NOT APPROVED FOR ALPHA

If NOT APPROVED:

List every blocking issue.

If APPROVED:

State that development is complete and only bug-fix patches should be allowed before the first production wedding.

Do NOT generate code.

Do NOT propose new features.

Stop after the report.
