Веб-разработка. Тестирование, доработка существующего продукта. ## Developer Task: End-to-End Testing & Debugging for Reqflow.ai ### Context Reqflow.ai is a B2B SaaS platform for automated requirements elicitation. It uses a multi-agent AI approach to conduct stakeholder interviews, extract requirements (Needs, FR, NFR, etc.), and generate IEEE 29148-compliant documents (BRD/SRS). **Tech Stack:** React + Vite + TypeScript | Supabase (Auth, DB, Realtime) | Supabase Edge Functions | TanStack Query --- ### Objective Validate all critical user journeys work end-to-end. Identify and document any broken flows, UI/UX issues, or backend integration failures. --- ### User Journeys to Test #### Admin Journey | Flow | Route | Key Actions | |------|-------|-------------| | **Auth** | `/signup`, `/login` | Sign up, log in, session persistence | | **Project Creation** | `/dashboard` | Create new project, verify it appears in list | | **Project Wizard** | `/projects/:id/setup` | Complete all 6 steps (info, users, entities, scenario, uploads, RACI), launch project | | **Overview Dashboard** | `/projects/:id/overview` | Verify tiles load (Jobs, Conflicts, Trace Health, Docs Pipeline) | | **Chat** | `/projects/:id/chat` | Send message, observe AI response streaming, entity extraction | | **Entities** | `/projects/:id/entities` | View/filter entities, check status transitions | | **Documents** | `/projects/:id/documents` | Generate document, review, approve (test state machine) | | **Traceability** | `/projects/:id/traceability` | Graph renders, filters work, table syncs | | **Settings** | `/projects/:id/settings` | Edit members, verify RACI is frozen post-launch, archive project | #### Stakeholder Journey | Flow | Route | Key Actions | |------|-------|-------------| | **Magic Link Invite** | `/invite/:token` | Receive invite, consume magic link, land in project chat | | **Restricted Access** | `/projects/:id/chat` | Verify limited sidebar (Chat, Documents only), no admin routes | | **Document Review** | `/projects/:id/documents/:docId` | View document, approve if Accountable (A) role | --- ### Success Criteria - [ ] Admin can complete full journey: signup → project → wizard → launch → chat → documents → approval - [ ] Stakeholder can: receive magic link → authenticate → chat → review documents - [ ] Realtime updates work (chat streaming, job status changes, entity updates) - [ ] No console errors, no network 4xx/5xx errors on happy path - [ ] RLS policies allow correct access (no “permission denied“ on valid operations) --- ### Deliverables 1. **Bug Report** (if any): Issue description, steps to reproduce, expected vs actual behavior 2. **Flow Completion Checklist**: Mark each journey as PASS/FAIL with notes 3. **Recommendations**: Any UX improvements or edge cases discovered.