# AptivaAI Test Components (Curated, Active Only) > Source of truth for what we **do test**. Keep this file tight and current. > Add a component/feature here **before** adding tests. ## βœ… Active Components ### A. Auth & Profile (server1) - **Feature A1**: SignUp β†’ SignIn (cookie) β†’ User Profile (JIT-PII: no `id`) - Test: `backend/tests/auth_signup_signin.mjs` ### B. Support & Messaging (server3) - **Feature B1**: `/api/support` auth, dedupe, rate limits, negatives (invalid category, short message) - Test: `backend/tests/support_limits.mjs` ### C. Subscription & Paywall (server3) - **Feature C1**: `/api/premium/subscription/status` returns `{ is_premium:false, is_pro_premium:false }` for new user; unauth β†’ 401 - Test: `backend/tests/subscription_status.mjs` --- ## 🟨 Pending Confirmation (do **not** test until moved above) - Premium Onboarding draft save/load (server3) - Career data & caching (server2) – salary & O*NET warm-cache - Loan Repayment & ROI (free) - Milestones & AI suggestions (server3) - Financial Projection service (frontend utils server3) - College Mode (premium) - Reminders & Twilio (server3) - AI chat risk analysis consumption (server3) - Nginx/Secrets/CSP checks - DB connectivity (MySQL SSL) & SQLite reads - Caching & file safety - Logging (rid present, no tokens/PII) > Move items up only after you confirm they’re current and in scope.