Skip to main content

QA Tester Guide

This page gives testers one guided path for validating the Builder Insights system.

It combines the most useful testing guidance from the mobile app and admin portal into a single flow.

Who This Is For​

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

Test Environments​

Mobile app​

  • TestFlight: https://testflight.apple.com/join/rAqHXs1Y
  • Demo login: demo@devrelinsights.app
  • Demo code: 999999

Admin portal​

  • URL: https://devrel-insights-admin.vercel.app
  • Demo login: demo@devrelinsights.app
  • Demo code: 999999

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

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
  2. mobile offline and sync check
  3. admin portal verification of captured data
  4. bug reporting and notes

15-minute smoke test​

1. Login and launch​

  • 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​

  • 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​

  • 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​

  • Log in to the admin portal
  • Open Insights
  • Confirm recently captured data is visible or eventually appears after sync

If any smoke item fails, stop and file a bug before running full regression.

Guided regression areas​

Mobile app​

Authentication and onboarding​

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

Capture and drafts​

  • 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

Attachments and detail flows​

  • photo library permission prompt appears when needed
  • camera permission prompt appears when needed
  • insight detail opens and shows expected content
  • insight edits persist

Events, dashboards, and profile​

  • events list loads and can set capture context
  • impact dashboard renders charts correctly
  • executive dashboard is only visible for manager/admin roles
  • profile shows sync state and user information
  • logout works

Security and app lock​

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

Admin portal​

Core navigation​

  • dashboard loads without errors
  • events page loads and supports search/filter
  • insights page loads and supports search/filter
  • leaderboard and world map load cleanly
  • settings page loads without broken sections

Data verification​

  • newly captured mobile insights appear in admin views after sync
  • insight details look complete and readable
  • event metadata used in mobile context matches admin data

Bug reporting​

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

What to include in bug reports​

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
  • 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​

SeverityMeaning
BlockerCore app use is stopped or data integrity is at risk
HighMajor feature broken with limited workaround
MediumImportant issue with workaround
LowMinor issue or polish gap

High-priority areas for release confidence​

  • launch and login
  • text capture
  • offline capture and reconnect sync
  • voice draft recovery
  • photo attachments
  • profile sync visibility
  • admin insight verification
  • Mobile App > Offline And Sync
  • Operations > QA For PM And Design
  • Operations > Bug Report Template
  • Operations > Testing And Release
  • Operations > Screenshots

Source references that informed this page:

These source paths 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