E2E User Journey Testing Guide

Overview

This document outlines the complete end-to-end user journeys for the GoGrab Space platform, ensuring all tools work together seamlessly in the multiverse architecture.

Testing Philosophy

"Test the user's experience, not just the code."

• Every test scenario represents a real user workflow
• Tests must pass through multiple tools (Editor, Singularity, Modularity, Launch Station)
• Context must persist across navigation
• Universe-scoped routes must work correctly

Manual Testing Checklist

Execute this checklist before each phase completion and before any release:

Core Navigation

• Can access /landing - platform landing page
• Can access /dashboard - main dashboard
• Dashboard shows list of universes
• Can access /universe/create - universe creation wizard
• Universe creation wizard works (3 steps)
• After creation, redirects to /space-map/:universeId

Space Map Journey

• Can access /space-map/:universeId - universe detail
• Universe detail shows galaxies and pages
• Can navigate to galaxy detail /space-map/:universeId/:galaxyId
• Can create new galaxy
• Can create new page
• Pages appear in Space Map after creation
• Universe context persists (shown in breadcrumb/header)

Editor Journey

• Can access /editor/:universeId/workspace - editor workspace
• If no page selected, page selector modal appears
• Can select existing page from modal
• Editor loads with selected page
• Can drag widgets from panel onto canvas
• Can configure widget properties
• Can save page (Ctrl+S or Save button)
• Saved changes persist after navigation away and back
• Universe context shows correct universe

Singularity Journey

• Can access /singularity/:universeId/dashboard - Singularity dashboard
• Dashboard shows existing flows
• Can navigate to /singularity/:universeId/logic-builder - Logic Builder
• Logic Builder loads correctly with canvas
• Can drag blocks from library onto canvas
• Can connect blocks via ports
• Can configure block properties
• Can save flow (Save button or Ctrl+S)
• Can execute flow (Run button)
• Execution results appear in panel
• Can navigate to /singularity/:universeId/database - Database Integration
• Can create database schema
• Universe context persists across all Singularity routes

Modularity Journey

• Can access /modularity - Modularity dashboard
• Dashboard shows existing modules
• Can click "Create Module" button
• Module builder opens with 3 tabs: Content, Logic, Deploy
• Content Tab: Shows pages from current universe
• Can select multiple pages
• Logic Tab: Shows flows from Singularity
• Can select multiple flows
• Deploy Tab: Can configure module manifest
• Can deploy module
• Deployed module appears in module list
• Deployed module routes are accessible

Launch Station Journey (Future)

• Can access /launch-station - Launch Station dashboard
• Dashboard shows all universes with deployment status
• Can click "Deploy Universe" button
• Deployment wizard opens (5 steps)
• Step 1: Domain configuration (subdomain or custom)
• Step 2: SEO settings (meta tags, OG image)
• Step 3: Analytics (Google Analytics, Plausible)
• Step 4: Performance (CDN, caching)
• Step 5: Review & Deploy
• Can deploy universe
• Universe status changes to "Published"
• Can access marketplace
• Can browse and install modules
• Can access template gallery
• Can apply template to universe

Test Scenarios

Scenario 1: Universe Creation to Space Map

Objective: Verify complete universe creation flow and redirect.

Steps:

1. Navigate to /dashboard
2. Click "Create Universe" button → redirects to /universe/create
3. Fill in universe details:
   • Name: "Test Universe"
   • Description: "E2E Test Universe"
   • Select "Blank Universe" template
4. Click through wizard steps (3 total)
5. Click "Create Universe" on final step
6. Expected: Redirects to /space-map/test-universe (or generated ID)
7. Expected: Universe appears in Space Map
8. Expected: Breadcrumb shows "Test Universe"

Pass Criteria:

• ✅ Universe created successfully
• ✅ Redirect works correctly
• ✅ Universe visible in Space Map
• ✅ Context service has correct universe ID

Scenario 2: Create Page in Editor

Objective: Create a page using the Editor and verify it appears in Space Map.

Steps:

1. Navigate to /space-map/:universeId
2. Click "Open Editor" button → redirects to /editor/:universeId/workspace
3. Page selector modal appears (no page selected)
4. Click "Create New Page"
5. Fill in page details:
   • Title: "Homepage"
   • Slug: "home"
6. Editor loads with empty canvas
7. Drag "Heading" widget from panel onto canvas
8. Configure heading text: "Welcome to Test Universe"
9. Click Save button (or Ctrl+S)
10. Expected: Success message appears
11. Navigate back to /space-map/:universeId
12. Expected: "Homepage" appears in pages list

Pass Criteria:

• ✅ Editor loads correctly
• ✅ Widgets can be dragged onto canvas
• ✅ Page saves successfully
• ✅ Page appears in Space Map
• ✅ Page persists after refresh

Scenario 3: Create Flow in Singularity

Objective: Create a logic flow in Singularity and save it.

Steps:

1. Navigate to /space-map/:universeId
2. Click "Open Singularity" button → redirects to /singularity/:universeId/dashboard
3. Click "Logic Builder" in navigation
4. Logic Builder canvas loads
5. Drag "Start" block from library onto canvas
6. Drag "Function" block onto canvas
7. Configure function block:
   • Name: "calculateSum"
   • Operation: "add"
   • Inputs: a=5, b=10
8. Connect Start block output to Function block input
9. Drag "Output" block onto canvas
10. Connect Function block output to Output block input
11. Click Save button
12. Name flow: "Simple Addition"
13. Expected: Flow saved successfully
14. Click Run button
15. Expected: Execution panel shows result: 15
16. Navigate to /singularity/:universeId/dashboard
17. Expected: "Simple Addition" flow appears in dashboard

Pass Criteria:

• ✅ Logic Builder loads correctly
• ✅ Blocks can be dragged and connected
• ✅ Flow saves successfully
• ✅ Flow executes correctly
• ✅ Flow appears in dashboard

Scenario 4: Package Module with Pages and Flows

Objective: Package a module that combines pages from Editor and flows from Singularity.

Prerequisites:

• At least 2 pages created in Editor
• At least 1 flow created in Singularity

Steps:

1. Navigate to /modularity
2. Click "Create Module" button
3. Module Builder opens
4. Content Tab:
   • Select "Homepage" page (checkbox)
   • Select "About" page (checkbox)
5. Click "Next" or switch to Logic Tab
6. Logic Tab:
   • Select "Simple Addition" flow (checkbox)
   • Check "Expose as Action"
   • Action name: "calculateSum"
7. Click "Next" or switch to Deploy Tab
8. Deploy Tab:
   • Module Name: "Basic Module"
   • Base Route: "/basic"
   • Click "Generate Manifest"
9. Review generated manifest
10. Click "Deploy Module"
11. Expected: Module deployed successfully
12. Expected: Module appears in Modularity dashboard
13. Try accessing /basic (module's base route)
14. Expected: Module homepage loads

Pass Criteria:

• ✅ Can select pages from Content tab
• ✅ Can select flows from Logic tab
• ✅ Manifest generates correctly
• ✅ Module deploys without errors
• ✅ Module routes are accessible
• ✅ Module pages render correctly

Scenario 5: Universe Context Persistence

Objective: Verify universe context persists across tool navigation.

Steps:

1. Navigate to /space-map/:universeId (Universe A)
2. Note universe ID/name in breadcrumb
3. Navigate to /editor/:universeId/workspace
4. Expected: Breadcrumb still shows Universe A
5. Navigate to /singularity/:universeId/logic-builder
6. Expected: Breadcrumb still shows Universe A
7. Navigate to /modularity
8. Expected: Breadcrumb still shows Universe A (or "All Universes")
9. Navigate to /dashboard
10. Select different universe (Universe B)
11. Navigate to /editor/:universeBId/workspace
12. Expected: Breadcrumb now shows Universe B
13. Expected: Editor loads pages from Universe B (not Universe A)

Pass Criteria:

• ✅ Universe context persists across navigation
• ✅ Context service updates correctly
• ✅ Each tool loads correct universe data
• ✅ Context breadcrumb updates correctly
• ✅ Switching universes updates all tools

Scenario 6: AI Integration (Future)

Objective: Use AI to generate widgets, flows, and modules.

Steps:

1. Navigate to /editor/:universeId/workspace
2. Click "AI Widget Styler" button
3. Describe widget: "Create a purple gradient button with rounded corners"
4. AI generates 3 style variations
5. Select variation and apply to widget
6. Navigate to /singularity/:universeId/logic-builder
7. Click "AI Assist" button
8. Describe function: "Validate email addresses and return true/false"
9. AI generates TypeScript function
10. Add function as block to canvas
11. Test function with sample email
12. Navigate to /modularity
13. Click "AI Module Generator"
14. Describe module: "Create a simple blog module with post list and detail pages"
15. AI generates complete module
16. Review and deploy module

Pass Criteria (Future):

• ✅ AI generates widget style variations
• ✅ AI generates executable TypeScript functions
• ✅ AI generates complete modules
• ✅ Generated code is production-ready
• ✅ Generated code uses theme utilities

Automated Testing Strategy (Future)

Unit Tests

• Test individual services in isolation
• Mock dependencies
• Cover edge cases

Integration Tests

• Test service interactions
• Test component communication
• Test data flow between services

E2E Tests (Playwright)

• Automate the scenarios above
• Run before each deployment
• Test critical paths only (to save time)

Visual Regression Tests

• Capture screenshots of key pages
• Compare against baseline
• Detect unintended visual changes

Test Data Requirements

Minimum Data for E2E Testing

Users:

• Test User 1: [email protected] (admin)
• Test User 2: [email protected] (viewer)

Universes:

• Universe 1: "Test Universe" (for creation/editing tests)
• Universe 2: "Demo Universe" (for context switching tests)
• Universe 3: "E-commerce Demo" (for module/template tests)

Pages (in Test Universe):

• Homepage (slug: home)
• About Page (slug: about)
• Contact Page (slug: contact)

Flows (in Test Universe):

• Simple Addition (basic math flow)
• Email Validator (string processing flow)
• Database Query (storage integration flow)

Modules:

• Basic Module (combines Homepage + About)
• Contact Module (Contact page + Email Validator flow)

Known Issues & Workarounds

Issue 1: Route Params Not Updating

Symptom: Navigation works but universe context doesn't update. Workaround: Use ActivatedRoute.params subscription in layout components. Status: FIXED in Singularity layout (Phase 0.1)

Issue 2: Page Selector Modal Doesn't Appear

Symptom: Editor loads without page selector modal. Workaround: Navigate to /editor/:universeId/workspace/:pageId with explicit page ID. Status: Needs investigation

Issue 3: Module Routes Not Accessible

Symptom: Deployed modules return 404 errors. Workaround: Manually add routes to app.routes.ts. Status: Needs DynamicRouteService implementation (Phase 1.2)

Test Execution Log

Next Steps

1. Phase 0.1: Fix Singularity routes ✅ COMPLETE
2. Phase 0.2: Fix Editor routes
3. Phase 0.3: Fix Space Map routes
4. Phase 0.4: Test all scenarios manually
5. Phase 1+: Continue with plan implementation

Contact

For questions or issues with testing:

• Documentation: docs/english/GoGrab-Space/
• GitHub Issues: Tag with testing label
• Slack: #qa-testing channel