Skip to content

Wireframe Test Plan

Aksel Tøndel Kirkhorn edited this page Apr 9, 2026 · 1 revision

Test Plan - User Testing of Wireframes

1. Purpose

The purpose of the tests is to evaluate whether the wireframes for the application support an intuitive, efficient and trust-inspiring user experience. The tests are conducted at different stages of the development of the wireframe, with the second test being performed on a nearly complete prototype.

In particular, we want to validate:

  • Understanding of the application's purpose
  • Navigation and information structure
  • User experience of trust and credibility
  • Implementation of the donation process

2. Test phases

2.1 Part 1: Early prototype

In this phase, an incomplete prototype with key main features implemented is tested. The goal is to evaluate basic structure and user understanding.

Test Objectives

  • The user understands within a few seconds what the application offers
  • The user understands how to create a user
  • The navigation is experienced as intuitive
  • The user is able to complete defined tasks without help
  • The user chooses the right navigation path on the first try

Focus: Information architecture and overall user flow.


2.2 Part 2: Complete prototype

In this phase, an almost completed wireframe is tested. The purpose is to evaluate the overall user experience and decision support before further development.

Test Objectives

  • The user experiences the information as credible
  • The user finds an organization based on category (e.g. poverty, war, hunger)
  • The user feels that they have sufficient information to make a donation decision
  • At least 80% of users complete the donation without help

Focus: Trust, information quality and efficient implementation of the donation process.


3. System Description

The application presents approved charities and allows users to:

  • Search for and sort organizations by category
  • Read information about the organization's purpose and use of funds
  • Add organizations to a favorite list
  • View previously visited organizations
  • Make a donation

The test focuses on wireframes and does not evaluate technical functionality. Comments about visual design are noted, but are not the main focus.


4. Test strategy

Moderated user testing is carried out.

  • The tests are performed individually
  • Participants are encouraged to think aloud
  • The test leader asks open and non-leading questions
  • The test leader avoids helping the user too early

Examples of questions during the test

  • "What do you expect to happen when you press there?"
  • "What feels unclear?"
  • "What are you thinking now?"

Observations, time spent and any problems are documented along the way.


5. Test environment

The tests are conducted in a quiet classroom environment where the user is given time to sit down with the application without interruptions.


6. Analysis and error handling

After each test:

  • Findings are collected and documented
  • Problems are grouped
  • Problems are prioritized by severity

Prioritization model

Severity Description
Critical Prevents the user from completing the task
High Causes great frustration
Medium Causes less confusion
Low Potential for improvement

The results are used to improve the wireframes before further development.


Test protocol – User testing of wireframes

1. Introduction (read aloud)

Hello, and thank you for participating in the test.

We are not testing you, but the solution itself. Therefore, there are no right or wrong answers.

We want you to say out loud what you think along the way: what you expect to happen, what seems unclear, and what you notice.

If something seems confusing or difficult, it is very helpful to us.

The test takes about 10–15 minutes. Do you have any questions before we start?


2. First Impressions (Part 1 – Early Prototype)

Show the home page.

Questions

  • What do you think this application is about?
  • What do you think you can do here?
  • Is there anything that is unclear at first glance?

Observe

  • How long does it take for the user to understand the purpose
  • If the user misunderstands something
  • What they notice first

3. Task 1 – Create user

Imagine that you want to use this application. How would you go about creating a user?

Follow-up questions

  • What do you expect to happen now?
  • What are you looking for?

Observe

  • If they find registration quickly
  • If concepts are understandable
  • If the navigation feels intuitive

4. Task 2 – Find organization

You want to donate to an organization that works with, for example, poverty. How would you find a suitable organization?

Follow-up questions

  • What do you expect to happen when you click there?
  • Do the categories feel logical?
  • Is something missing?

Observe

  • Whether they use search or category
  • Whether filtering works intuitively
  • Where they stop

5. Task 3 – Assess credibility

Before you donate, you want to make sure that the organization is approved and trustworthy.

Follow-up questions

  • Do you feel you have enough information?
  • Is there anything that makes you unsure?
  • Where would you expect to find information about approval?

Observe

  • Whether they find approval information
  • Whether they express confidence or uncertainty
  • Whether the information is clearly placed

6. Task 4 – Making a donation

You have now chosen an organization and want to donate. Show how you would make the donation.

Along the way

  • What do you expect to happen now?
  • Does the process feel simple or complicated?
  • Does anything seem unnecessary?

Observe

  • If they complete without help
  • If they become unsure of steps
  • If anything seems unclear in the process

7. Closing questions

  • How did you experience the solution overall?
  • What worked well?
  • What would you improve?
  • Would you use this solution in real life? Why/why not?
Clone this wiki locally