> For the complete documentation index, see [llms.txt](https://t420.gitbook.io/t420/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t420.gitbook.io/t420/external_tester_guide.md). # FleetOS External Tester Guide > URL: Time: \~20 minutes ## Setup * Use Chrome (or any modern browser) * Use incognito/private window for clean tests * Have WhatsApp on your phone for link tests *** ## Test Checklist ### A. Landing Page * [ ] Page loads at * [ ] Shows FleetOS branding (logo in nav bar) * [ ] Browser tab says "FleetOS | From Chaos to Compliance" * [ ] Green F favicon visible in browser tab * [ ] "I'm a Supplier" and "I'm a Fleet Operator" buttons visible * [ ] "Login" button visible in navigation ### B. Daily Access Login * [ ] Click "Login" in nav bar * [ ] Email input appears with placeholder "" * [ ] Enter a company email (e.g. ) and click GO * [ ] Dashboard loads (if company exists in DB) or account is created * [ ] Log out * [ ] Enter a gmail address (e.g. ) and click GO * [ ] Prompted for company name before proceeding * [ ] Enter company name, then dashboard loads ### C. Sign Up (pick one role) * [ ] Click "I'm a Supplier" (or "I'm a Fleet Operator") * [ ] Fill in company name, email, submit * [ ] Dashboard loads with demo data * [ ] Your name/company visible in header ### D. Dashboard - Jobs Tab * [ ] Demo jobs visible (seeded automatically) * [ ] Tap a job card to expand it * [ ] ACCEPT / START / DONE buttons visible (note input optional) * [ ] DECLINE (or CAN'T HELP) button visible * [ ] Tap ACCEPT on a pending job - status updates * [ ] Tap DONE on an in-progress job - status updates ### E. Dashboard - Contacts Tab * [ ] Tap "Contacts" tab * [ ] Contacts list visible (or empty state with "Add" option) * [ ] Tap a contact to see details * [ ] Edit details (e.g. name or phone), save * [ ] Refresh page - changes persist * [ ] Add new contact form works ### F. Create a Job (Supplier view) * [ ] Tap "ADD JOB" button * [ ] Select existing contact (phone auto-filled if on file) * [ ] Fill vehicle, location, description * [ ] Submit - job appears in list * [ ] WhatsApp share option shown after creation ### G. Assign a Job * [ ] Expand a job, tap ASSIGN * [ ] Team members shown in overlay * [ ] Tap a name - "ASSIGNED TO \[NAME]" banner appears * [ ] Tap "+ ADD NEW" - add by phone - appears in list ### H. Magic Link (ask another tester to help) * [ ] Create a job and copy the respond link * [ ] Send to another person (via WhatsApp, email, etc.) * [ ] They open it - see request details (no login required) * [ ] They tap ACCEPT - "RESPONSE SENT" confirmation shown * [ ] They can also tap CAN'T HELP ### I. Contact Actions (Fleet view) * [ ] Tap CONTACT on a job card * [ ] Phone number shown (tappable to copy) * [ ] Message input for WhatsApp available * [ ] REQUEST UPDATE button shows SENDING/SENT or NO PHONE ### J. Logout & Session * [ ] LOG OUT button works * [ ] Refresh after logout - stays on landing (not auto-redirected) * [ ] Log back in - session restored, dashboard loads *** ## Bug Report Format If something doesn't work: ``` What you tried: (exact steps, e.g. "Tapped ACCEPT on the first job card") What you expected: (e.g. "Status should change to Acknowledged") What happened instead: (e.g. "Nothing happened, button stayed the same") Screenshot: (if possible) Browser + device: (e.g. Chrome on iPhone 14, Safari on MacBook) ``` Send reports to the team Slack channel or email the development team. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://t420.gitbook.io/t420/external_tester_guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.