QA Tester Guide

Guided validation path

This page gives testers one structured path for validating the Builder Insights system across both the mobile experience and the admin control plane.

Best fit for this guide

• internal testers validating preview builds
• product and design teammates doing smoke or regression passes
• engineering and release owners coordinating signoff

Test environments

Surface	Access
Mobile app	TestFlight: https://testflight.apple.com/join/rAqHXs1Y
Mobile demo account	demo@devrelinsights.app / 999999
Admin control plane	https://devrel-insights-admin.vercel.app
Admin demo account	demo@devrelinsights.app / 999999

Legacy naming

The admin hostname and demo credentials still use legacy devrel identifiers during the transition.

Decision

Core testing principles

• treat offline capture as a product guarantee
• prefer physical devices for microphone, camera, biometrics, and resume behavior
• test one happy path and one failure or offline path for major workflows
• log exact repro steps while testing
• stop and file a bug early if a smoke-test blocker appears

Suggested test order

1. Mobile smoke test

Confirm launch, login, primary surfaces, and one successful saved insight.

2. Offline and sync check

Create a record offline, restore connectivity, and verify the queue reconciles cleanly.

3. Admin verification

Confirm the captured record becomes visible and readable in the admin control plane.

4. Bug reporting and notes

If something breaks, file it immediately with enough context that triage can start without guesswork.

15-minute smoke test

1. Login and launch

The app should feel stable before you spend time exploring deeper flows.

• [ ] App launches cleanly
• [ ] Login accepts demo@devrelinsights.app
• [ ] Code 999999 signs in successfully
• [ ] Home, Capture, Context, Impact, and Profile load

2. Create one mobile insight

Use one short, realistic sample so the save path and resulting data stay easy to verify later.

• [ ] Open Capture
• [ ] Enter a short text insight
• [ ] Choose type, product area, sentiment, and priority
• [ ] Save successfully
• [ ] Confirm the saved insight appears in the app

Suggested sample text: Builder asked for clearer Vector Search indexing guidance for multi-field schemas.

3. Offline check

This validates one of the highest-risk promises in the product.

• [ ] Turn on airplane mode
• [ ] Create one new insight while offline
• [ ] Pending count increases
• [ ] Turn network back on
• [ ] Pending count returns to zero after sync

4. Admin confirmation

Use the admin control plane as proof that the system completed the full end-to-end loop.

• [ ] Log in to the admin control plane
• [ ] Open Insights
• [ ] Confirm recently captured data is visible or eventually appears after sync

Risk

Stop early on smoke blockers

If any smoke item fails, stop and file a bug before running deeper regression. Continuing can waste time and make the original failure harder to isolate.

Guided regression areas

Mobile: authentication and onboarding

Confirm the first-run and sign-in experience is understandable, correct, and role-safe.

• [ ] invalid email domains are rejected
• [ ] invalid codes show a clear error
• [ ] onboarding appears on a fresh install
• [ ] onboarding can be skipped and stays dismissed

Mobile: capture and drafts

This area carries high product and trust risk because it touches the core value of the app.

• [ ] text capture saves online
• [ ] text capture saves offline
• [ ] voice recording creates a transcription or recoverable draft
• [ ] pending recordings can be completed or discarded
• [ ] similar insight warning appears for near-duplicate content when applicable

Mobile: attachments, dashboards, and profile

Check the supporting surfaces that turn capture into a complete, trustworthy experience.

• [ ] photo and camera permission prompts appear when needed
• [ ] insight detail opens and edits persist
• [ ] events list loads and can set capture context
• [ ] impact dashboard renders charts correctly
• [ ] profile shows sync state and user information
• [ ] logout works

Mobile: security and app lock

Use physical devices where possible, because simulator coverage here is usually not enough.

• [ ] biometric or PIN lock can be enabled on supported devices
• [ ] relock behavior works after backgrounding
• [ ] failed unlock lockout behaves correctly

Admin control plane: navigation and verification

This confirms whether synced data becomes usable, visible, and operationally meaningful.

• [ ] dashboard loads without errors
• [ ] events and insights pages load with search/filter support
• [ ] leaderboard, world map, and settings load cleanly
• [ ] newly captured insights appear in admin views after sync
• [ ] event metadata matches what mobile users selected

Bug reporting entry points

Make sure testers can actually report what they find while context is still fresh.

• [ ] bug report FAB opens on the admin control plane
• [ ] mobile shake-to-report flow works on device
• [ ] reports include enough context for triage

What to include in bug reports

QA check

Every report should include

• short title
• build or environment used
• device and OS for mobile issues
• account and role used
• network state
• exact repro steps
• expected result and actual result
• screenshot or recording when helpful

For sync or offline issues, also include:

• whether the item was created online or offline
• pending count before and after
• whether the issue survived app relaunch

Severity guide

Severity	Meaning
Blocker	Core app use is stopped or data integrity is at risk
High	Major feature broken with limited workaround
Medium	Important issue with workaround
Low	Minor issue or polish gap

High-priority release confidence areas

• launch and login
• text capture
• offline capture and reconnect sync
• voice draft recovery
• photo attachments
• profile sync visibility
• admin insight verification

Related references

• Mobile Experience > Offline And Sync
• Operations Runbooks > QA For PM And Design
• Operations Runbooks > Bug Report Template
• Operations Runbooks > Testing And Release
• Operations Runbooks > Screenshots

Source references that informed this page still use legacy repo names:

• devrel-insights/docs/TESTER-GUIDE.md
• devrel-insights/docs/QA-README.md
• devrel-insights/docs/BUG-REPORTING.md
• devrel-insights/docs/QA-TEST-MATRIX.md
• devrel-insights-admin/docs/TESTER-GUIDE.md