2.0 KiB
2.0 KiB
Manual Edge and physical-device checklist
Use the seeded sample data. Do not mark a row complete without a real session. Capture the application and the relevant OS/browser information screen without personal information.
Session metadata
| Field | Device A | Device B |
|---|---|---|
| Manufacturer/model | PENDING | PENDING |
| Operating system/version | PENDING | PENDING |
| Native display resolution | PENDING | PENDING |
| Display scaling | PENDING | PENDING |
| Browser and exact version | PENDING | PENDING |
innerWidth × innerHeight |
PENDING | PENDING |
| Tester/date | PENDING | PENDING |
Principal workflow
- Load sample data and confirm four goals/nine tasks.
- Create a goal and confirm required-field validation is announced and visible.
- Add, edit, complete, search/filter and delete a task.
- Reload and confirm changes persist.
- Export a backup, restore sample data, then import the backup.
- Use Tab/Shift+Tab/Enter/Escape and confirm logical focus with visible indicators.
- Inspect long titles, date fields, modal fit, scrolling and 125% zoom.
- Confirm no page-level horizontal overflow.
- Confirm the application console has no errors.
Edge developer-tools evidence
- Capture
edge://settings/helpwith the stable version visible. - Capture the seeded dashboard in Edge.
- Capture DevTools Console after the principal workflow.
- Capture Application → Local Storage showing
learning-planner.state(avoid expanding sensitive data). - Record computed Grid columns at the device viewport.
- Record any difference from Chromium/Firefox and the retest result.
Required screenshot names
device-a-system.png, device-a-dashboard.png, device-b-system.png, device-b-dashboard.png, browser-edge-dashboard.png, browser-edge-console.png, browser-edge-storage.png.
After completing the sessions, update test-log.md, replace pending text in the device/browser evidence documents, regenerate DOCX/PDF files and tag the assessor-ready revision.