🏠 QejaVerse UAT Testing Guide
Everything you need to know before you start testing
What is QejaVerse?
QejaVerse is a real estate platform that connects Property Developers, Real Estate Agents, Legal teams and Property Buyers (Clients) through the full property purchase journey — from discovery to signed sale agreements.
👥 Who are the users?
🏗️ Developer
Who: Property development company staff
Arrives via: Self-signup on the platform
- Creates projects & adds units
- Sets up payment plans & pricing
- Invites Agents to sell on their behalf
- Books units for clients & sends invitations
- Manages full sales pipeline
- Invites Lawyers to review legal docs
🤝 Agent
Who: Independent real estate agents
Arrives via: Self-signup OR invited by Developer
- Gets invited to projects by Developers
- Represents Developer to buyers
- Manages leads & client relationships
- Earns commission on sales
- Can self-signup & request to join projects
🏡 Client
Who: Property buyers
Arrives via: Developer invitation OR marketplace self-register
- Browses properties on marketplace
- Receives portal invitation from Developer
- Completes identity verification & plan selection
- Signs offer letters & sale agreements
- Makes payments per schedule
- Tracks ownership journey on dashboard
⚖️ Lawyer
Who: Legal document reviewers
Arrives via: Magic-link invitation from Developer/Admin
- Receives magic-link invitation
- Reviews offer letters & sale agreements
- Approves or requests changes
- Has dedicated legal review dashboard
🚪 How do users get access?
There are 4 distinct entry points into the platform:
1️⃣ Self-Signup (the "front door")
- User visits the app → clicks Sign Up
- Creates account with email/password OR Google OAuth
- Accepts Terms & Conditions
- Chooses their role (Developer or Agent)
- Lands on their role dashboard
2️⃣ Invitation Links (the "side doors")
- Team Invitation: Developer invites Agent/Manager to a project via email. Invitee clicks link, signs up (or logs in), gets the role automatically.
- Client Portal Invitation: Developer books a unit for a client → system sends invite email → Client clicks link, verifies phone via OTP, completes onboarding wizard.
- Lawyer Invitation: Admin/Developer sends a magic-link → Lawyer clicks → gets access to legal review dashboard.
3️⃣ Marketplace Discovery (the "discovery door")
- Anonymous user browses public project listings at
/discover
- Shows interest in a property → completes 9-question qualification flow
- If scored "Hot" lead → offered to self-register as Client
- If "Warm/Cold" → an agent will contact them
4️⃣ Add Role (existing users)
- A user who already has one role (e.g. Agent) can add another role (e.g. Developer)
- Phone verification required
- Both roles accessible via a role switcher in the navigation
⚠️ Key things to know while testing
| T&C Gate |
Every new user MUST accept Terms & Conditions after first login. You cannot bypass this. |
| OTP Verification |
Phone verification is required for invitations and marketplace flows. |
| Emails & OTPs |
This is staging — emails and OTPs go to the actual address/number you enter. If using fake credentials, retrieve OTPs from the backend (see below). |
| Google OAuth |
Works with any real Google account. Creates a platform account on first use. |
| Invitation Tokens |
Links expire after 30 days. Email must match exactly. |
| Role Gate |
Only appears for self-signup users. Invited users skip it (role is pre-assigned). |
🔑 How to retrieve OTPs and verification codes
When testing with emails/phones that can't receive messages:
- Log into Frappe desk at staging.qejaverse.com/app
- In the search bar, type "OTP" and open the OTP list
- Find your entry by email or phone number
- The code and expiry time will be visible
💡 If you use a real email address, OTPs will arrive in your inbox normally.
🔗 URLs you'll use
| URL |
Purpose |
/ |
Public homepage |
/signup |
Create new account |
/login |
Sign in to existing account |
/discover |
Browse marketplace (no login needed) |
/portal/invite?token=xxx |
Client invitation landing |
/onboarding/agreement |
T&C acceptance (auto-redirected here) |
/client/dashboard |
Client home |
/agent/dashboard |
Agent home |
/manager/dashboard |
Developer home |
🖥️ Your testing environment
🐛 Bug Reporting
When you find a bug:
- Mark the test case as FAIL in the spreadsheet
- In the Notes/Bugs column, include:
- What actually happened (vs. what was expected)
- Screenshot if possible (paste link or attach)
- Browser you used (Chrome, Safari, etc.)
- Whether you were on mobile or desktop
- If it's a blocker (prevents you from continuing), flag it immediately to the test coordinator
✅ RYou are now ready to open your assigned test sheet and start working through it row by row.