Self-train · Analyst-led · All five teams · Human users welcome

UAT Participant Guide

Testing is how we cut operating costs, grow safely, and keep everyone able to earn and be rewarded continuously. Analysts lead — Data, System, User, Security, and App teams execute — humans protect their own profile & business.

Start self-train quizzes 🎮 Open UAT features PDF / guide page Chat: uat help

🎯 Why this is critical (and exciting)

Cost: One hour of UAT can save days of production outages and support load.
Growth: Features reach live users faster when critical paths are proven.
Earn: Stable chat, eShop, and support shifts mean continuous 3% trading and paid support work.
Trust: Colourcraft-style gate = sessions + sign-off + PROD backup before sync.

Golden rule: Nothing goes to PROD without documented steps, critical Pass sessions, required sign-offs, and automatic PROD backup first. Timeline history is never deleted.
Dev→QA: approve sync gate in chat/dashboard — no auto-rsync.

💬 Conduct feature UAT in chat (main UI)

Chat is the preferred interface for feature UAT on web and mobile hubs:

uat list — see features ready for testing
start uat — open your session
pass 1 · fail 2 reason… — mark each step
uat done — submit (critical fails → Analyst task)

Analysts / core team:

qa status · qa failures · qa run
qa sync list · approve sync CODE · reject sync CODE
Dashboard: BusinesSite → UAT Testing → QA Agents

Open chat Full guide

🧭 Analysts — test managers & lead testers

You design the pack and coach the five teams. Own the release quality.

Watch QA Agents → Runs (or chat qa status) for Dev regressions.
Backend: BusinesSite → UAT Testing → Releases → create release.
Add Features + steps (instructions, test data, expected, critical?, modules).
Release for UAT — broadcasts chat/push; teams use uat list.
Watch Timeline history as sessions and steps land.
Dev green → Request Dev→QA sync → approve sync (gate only) → host sync.
On QA: collect Sign off…; then Promote to PROD (backup then sync).

Five teams — what each tests

📊 Data

Masters, ranks, reports, migrations. Use step test data. Fail with numbers: expected vs actual.

⚙️ System

Instances, gate runner, backup path, promote order: backup → sync → upgrade → restart.

👤 User

🔒 Security

Portal shoppers vs internal humans; owner claim docs; no Settings auto-grant; manager-only promote.

📱 App

RC1/TA8 commercial · RC2/TA13 tourism (TA5 frozen) · 📎 photos · chat intents · eShop · tourism packages.

🏢 Human users — profile & business/service

You protect your life profile and your businesses.

People = human profile (internal user). Businesses & Services = shops (eShop is one type).
eShop name ≠ personal name; choose mall (free) or domain (costs).
Co-hosted: join business Colourcraft Auto as owner + registration docs + certified ID + affidavit (same date).
Test on QA / this site — never “try breaks” only on live customers.

End-to-end flow (remember this)

Draft release → Features + steps
  → Release for UAT
  → Tester sessions (Pass/Fail)  → Timeline
  → Sign-offs (key user + final)
  → Promote: BACKUP PROD → QA→PROD sync → upgrade
  → Refresh promote status → Timeline: backup_ok / sync_ok / deployed

🏆 Motivation & continuous rewards

Pass quizzes (≥70%) on the train page → badges on your trail.
Catch a critical fail early → fewer production incidents → more trust and trading volume.
Support providers: stable platform = more paid 3h shifts.
Business owners: digitised customers/suppliers/staff = lower admin cost.

Play the quizzes now