Validate launch readiness with fresh-user onboarding test #33

New Issue

2026-03-03T22:24:32+01:00

libretech commented

2026-03-03 22:24:32 +01:00

Parent

#28 — Epic: Prepare public launch, community infrastructure, and initial user onboarding

Summary

Perform a structured quality assurance pass to validate that the full onboarding experience works end-to-end for a brand-new user. This involves testing the complete flow from landing page through signup, first login, onboarding walkthrough, creating first notes, and consulting the documentation. Also validate that community infrastructure (issue templates, contributing guide) works correctly from a contributor's perspective.

Acceptance Criteria

Fresh-user test completed on a staging or production-like environment
Full signup-to-first-note flow works without errors or confusion
Onboarding flow displays correctly on desktop (Chrome, Firefox) and mobile (iOS Safari, Android Chrome)
Documentation (user guide, self-hosting, API, contributing) is accessible and accurate
Issue templates render correctly when a new contributor opens an issue
PR template renders correctly when a contributor opens a pull request
Any issues found are filed as separate bug reports
Test results documented in a summary report or checklist

Dependencies

#29 (documentation) — docs must be written before they can be tested
#30 (v0.1.0 release) — release artifacts should be available for self-hosting doc validation
#31 (community infrastructure) — templates must exist before they can be tested
#32 (onboarding flow) — onboarding must be implemented before it can be tested

Scope Notes

This is a manual QA task, not automated testing
Does not include load testing or performance benchmarking
Does not include security audit (that should be a separate concern)
Ideally performed by someone who has not been involved in development

## Parent #28 — Epic: Prepare public launch, community infrastructure, and initial user onboarding ## Summary Perform a structured quality assurance pass to validate that the full onboarding experience works end-to-end for a brand-new user. This involves testing the complete flow from landing page through signup, first login, onboarding walkthrough, creating first notes, and consulting the documentation. Also validate that community infrastructure (issue templates, contributing guide) works correctly from a contributor's perspective. ## Acceptance Criteria - [ ] Fresh-user test completed on a staging or production-like environment - [ ] Full signup-to-first-note flow works without errors or confusion - [ ] Onboarding flow displays correctly on desktop (Chrome, Firefox) and mobile (iOS Safari, Android Chrome) - [ ] Documentation (user guide, self-hosting, API, contributing) is accessible and accurate - [ ] Issue templates render correctly when a new contributor opens an issue - [ ] PR template renders correctly when a contributor opens a pull request - [ ] Any issues found are filed as separate bug reports - [ ] Test results documented in a summary report or checklist ## Dependencies - #29 (documentation) — docs must be written before they can be tested - #30 (v0.1.0 release) — release artifacts should be available for self-hosting doc validation - #31 (community infrastructure) — templates must exist before they can be tested - #32 (onboarding flow) — onboarding must be implemented before it can be tested ## Scope Notes - This is a manual QA task, not automated testing - Does not include load testing or performance benchmarking - Does not include security audit (that should be a separate concern) - Ideally performed by someone who has not been involved in development

libretech added the phase-6 task labels 2026-03-03 22:24:32 +01:00

libretech referenced this issue from a commit

2026-05-02 14:50:46 +02:00

Add CHANGELOG and launch validation checklist

libretech closed this issue

2026-05-03 09:12:41 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: public/librenotes#33