Testing Results - NTNU-IE-IIR/prosjekt-idata1005-2025-abc GitHub Wiki
Testing
Why we test
Our goal is to catch usability and functional issues early, so that fixes are cheaper than post‑launch rewrites and, ultimately, so end‑users can succeed on their first try.
Test phases completed so far
Phase | Date | Scope | Participants | Outcome | Report |
---|---|---|---|---|---|
Wireframe Usability Test | 2025‑02‑15 | Figma wireframes (nav + core flows) | 1 users | Exposed 3 critical nav dead‑ends | Wireframe Test |
MVP Usability Test | 2025‑04‑05 | Clickable MVP | 2 users | High task‑completion, but low button affordance | MVP Usability Test Report |
Key improvement already in flight: add hover styling + pointer cursor to all interactive buttons.
Methodology at a glance
- Recruit target users that match our primary persona.
- Design task scenarios around top “jobs‑to‑be‑done.”
- Moderate 10-30 min think‑aloud sessions.
- Capture video + notes in Lookback.
- Synthesize findings within 48 h (severity, evidence, fix ideas).
- Prioritize fixes in the product backlog.