Web beta testing

Use this guide to test Badger before school starts.

This page gives internal testers one clear path through the product, one feedback format, and the safety boundaries we need to preserve during beta.

Start beta test Open feedback template

Beta preflight

Confirm production before testing.

Start every internal test from the same production path. This keeps feedback tied to the deployed web beta instead of local, preview, or cached browser state.

Use production only

Open badger-ecru.vercel.app or the connected custom domain so reports match what teammates can see.

Check status first

If a page is blank or slow, check production status before retrying the same action.

Keep one test email

Use the same email through signup, confirmation, login, and password recovery.

Report before switching paths

If confirmation, login, or profile setup blocks testing, report the exact URL before creating another account.

Production status Confirmation help Password recovery Report blocker

Live check

Session tracker

Track one complete beta route.

Use this during teammate testing so every session covers the same account, coach, journal, Stories, People, and Settings path.

0/6 done

Ready to copy progress.

Account and confirmationCreate an account or log in with one test email.Open

Profile and SettingsFinish profile setup, then check Settings before testing features.Open

Meli coachStart or resume one coach conversation and check retry clarity.Open

Dear Me journalCreate, edit, search, and delete one private journal entry.Open

Stories communityPost, reply, support, remove support, and report a concern.Open

People and sign outCheck Connections, then sign out before handing over the device.Open

Badger web beta session progress
Completed: 0/6

Completed items:
- None yet

Remaining items:
- Account and confirmation
- Profile and Settings
- Meli coach
- Dear Me journal
- Stories community
- People and sign out

If anything blocked testing, paste this with the issue report from /support.

Teammate invite pack

Share one clean beta handoff.

Use this when asking a teammate to test the production web beta. It keeps the invite, test path, safety note, and feedback format in one message.

Production URL

https://badger-ecru.vercel.app

Quick link

Tester start page

Quick link

Production status

Quick link

Feedback builder

Badger web beta is ready for internal testing.

Production URL: https://badger-ecru.vercel.app
Start here: https://badger-ecru.vercel.app/beta

Test path:
1. Signup or login
2. Profile and Settings
3. Meli coach
4. Dear Me journal
5. Stories community
6. People and Connections
7. Support report

Please use one email through signup, confirmation, login, and recovery.
If the site is slow or blank, check https://badger-ecru.vercel.app/status before retrying.

For issues, use https://badger-ecru.vercel.app/support and include URL, device, browser, account email, severity, expected result, actual result, and whether refresh helped.

Safety note: do not share passwords, private Dear Me text, full Meli conversations, or screenshots exposing another person.

Ready to copy invite.

August 3 beta candidate gate

Ship the first candidate only after these pass.

Use this gate at the end of each launch-readiness pass. If any item fails, keep fixing the web beta before inviting a larger teammate group.

Check production Run route Triage reports

Public entry is stable

Landing, beta guide, signup, login, support, and status load from production without blank screens.

One account can finish the route

A tester can use one email through signup, confirmation or login, profile setup, Meli, Dear Me, Stories, People, Settings, and sign out.

Safety controls are visible

Report actions, support guidance, privacy boundaries, and emergency language are present before wider testing.

Feedback is reproducible

Every blocker report includes URL, device, browser, account email, severity, expected result, actual result, and refresh result.

Responsive QA pass

Check mobile, tablet, and desktop before the beta candidate.

Use this on production after the core route works so layout issues are separated from account or API blockers.

Current viewportChecking current viewport.

Current hostChecking current host.

Phone pass

390px

Use a narrow viewport around 390px wide. Confirm landing, signup, beta guide, support, and status stack without horizontal scrolling.

Tablet pass

768px

Use a medium viewport around 768px wide. Confirm cards reflow cleanly and buttons stay reachable.

Desktop pass

1280px

Use a wide viewport around 1280px wide. Confirm hero panels, app cards, and handoff sections keep readable line lengths.

Signed-in pass

same viewport

After one account works, check Meli, Dear Me, Stories, People, and Settings at the same viewport.

Start responsive route Check production status Report layout issue

Public browser QA matrix

Mark each public route before teammate handoff.

Use this after the responsive pass so blank screens, slow pages, and route-specific layout issues are tracked separately from signed-in product feedback.

Browser QA hostChecking browser QA host.

Browser QA viewportChecking browser QA viewport.

0 pass0 needs fix0 blocked

Copy browser QA matrix

Landing

Hero, signup link, beta link, and safety copy render without sideways scrolling.

Beta guide

Tester route, feedback format, safety boundaries, and launch links stay visible.

Signup

Onboarding steps, browser draft, email preflight, and recovery links are reachable.

Confirmation help

Confirmation recovery explains the next action without asking testers to make a new account.

Password recovery

Reset path keeps the same email and explains expired-link recovery.

Support

Feedback builder captures host, viewport, severity, expected result, and actual result.

Status

Production route check and beta candidate decision note are available.

What to test first

Cover the full web beta path.

Start with the full web beta path: create an account, finish profile setup, start one Meli coach conversation, create one Dear Me journal entry, and use Stories to post, reply, support, and report.

After the core loop works, check Connections and Settings so we know account settings, safety controls, and sign out are ready for a small internal beta group.

How to send feedback

Make each report reproducible.

For every issue, include the page or URL, device, browser, account email, severity, what you tried, what happened, what you expected, and whether refreshing fixed it.

Use blocker when you cannot finish the task, confusing when you recover but feel unsure, and visual when the page works but looks wrong or does not match the Freely Feeling design direction.

Blocker

You cannot finish the task, save, submit, or reach the next step.

Confusing

You can recover, but the page does not make the next action clear.

Visual

The page works, but spacing, color, copy, or responsiveness feels wrong.

Safety boundaries

Keep tester data private.

Do not send passwords, private Dear Me journal text, full Meli conversations, or screenshots that expose another person's private information.

Badger is not an emergency service. If someone might be in immediate danger, contact local emergency services or a trusted adult right away.

Known beta limits

Test web first, then widen carefully.

The first internal beta is focused on the web app. Native mobile work is paused for now so the team can avoid App Store and TestFlight process risk before school starts.

Private messaging is not part of this beta. Connections can be tested as a lightweight people surface, but we should not present it as a finished direct-message product yet.

Launch links

Use these links during internal testing so feedback points to the same web beta path.

Start signup Log in Send feedback Safety guide Check production status