Test

What is Testing in UX/UI Design?

Testing is the final step in the Design Thinking process, where you test the prototype with real users to gather feedback and evaluate the effectiveness of the design solution.

In other words, this is the time you “bring the product into the light” to see what real users think, do, and whether they encounter any difficulties when using it.

The Goals of Testing

• Determine whether the prototype solves the user problem

• Explore unforeseen user behaviors/habits

• Validate (or invalidate) previous assumptions

• Find errors and unclear areas to improve

Testing is not just asking “Do you think it's okay?”

Don't mistake testing for simply giving the prototype to users and asking them if they like it. What users say may be one thing, but actual behavior can be very different.

An effective testing session usually includes:

• A specific scenario (e.g.: “Please schedule an appointment with the dermatologist this week.”)

• Observing behavior, noting where users struggle

• Recording completion times and errors that occur

• Asking for additional impressions, but not leading them

Example

Suppose you are designing a spa booking app. At the prototype stage, users can select services, appointment times, and make payments.

During testing, you realize:

• Users do not recognize the “Confirm” button because its color blends with the background

• They select the wrong time because the calendar display is unclear
  → This is valuable information that helps you adjust the design before going into actual development.

Not just checking, the Testing phase is also for learning

Don't be afraid of users “failing” during testing. Every mistake and every obstacle is a lesson that helps improve the product. The important thing is:

Test early – test often – the cost of fixing mistakes is low
The longer you postpone testing, the higher the cost of fixing mistakes.

Testing is the step of “putting users at the center” in the truest sense of the Design Thinking process. It helps you avoid “costly mistakes” by learning from the users themselves. A well-tested product will understand users better, serve better, and be more successful.