How to perform Testing in UX?

“you are not testing the user, the user is testing the design”
With the growth of the UI\UX design field, companies started realizing the importance of the UX discipline. Before launching any of the products or services this becomes very much crucial to actually test the implementation and ideas that are put to develop a particular product.
A usability issue that goes unnoticed can easily cause a large number of users to abandon a digital product or service. That is why Testing is so important, it gives you the chance to evaluate your design, your assumptions and to understand the user feedback to enure the acceptance of your future product.
What is Testing?
Testing is the process of collecting information about usability and overall user experience from actual users during the design process.
In Testing, UX practitioner:
i. Observe the user performing tasks.
ii. Collect data on user thought.
iii. Gathers user feedback.
There are two main types of testing in UX Research:
a. Existing system
b. System in development
How is Testing different from UX Researcher?
User testing refers to a specific method for evaluation of an interface while user research incorporates a group of methodologies for evaluation of a system/interface that includes user testing, interviews, surveys, and others. So, user testing is just a type of user research method.

Testing is a part of UX Research, that involves the following:
i. Observes users performing tasks on system.
ii. Learns what works and what doesn’t work.
iii. Observe where users have difficulties.
iv. Make notes of incident areas.
Testing - Observations types
UX practitioner needs to make certain observations in order to deliver a good product that fulfills all the user requirements which are needed in developing a market-like product. The certain observations that need to be taken under consideration are:
i. Product effective at error detection?
ii. Product effective at error recovery?
iii. COnventions memorable.
iv. Task Enjoyable?
v. Task difficulty?
vi. Unsuccessful steps?
Observation Process:

Observation research is a qualitative research technique where researchers observe participants’ ongoing behavior in a natural situation. The purpose of this type of research is to gather more reliable insights. In other words, researchers can capture data on what participants do as opposed to what they say they do.
- Users are not led in the tasks assigned.
- Users must figure out tasks of their own.
- Users should “think aloud”.
Steps to include while testing
These steps are needed to take out successful testing. These are before the testing session, During the testing session, after testing session, Debrief, Reviewing the test, Reporting. User testing is the way to ensure that we create products that work, and work for the people.
User testing is known as a lot of things: usability testing, product testing, design viability, ux testing, etc. but the end goal is the same, to test how the users interact with the design.
Before the test session:
A usability test session is undoubtedly the most crucial step in the whole process. In this stage, ensure that you have clearly defined goals. Usability testing is done in the initial stages to identify roadblocks or changes that would cost a lot in the final stages of development.
i. Check Prototype.
ii. Check recording equipment.
iii. Prepare a script.
iv. Clear history
During the test session:
Not everyone is the target audience for say, an online toy store. For enterprise products, this step is somewhat simpler, as the target audience is pre-defined and all you need to do is identify a good mix of users to recruit for testing.
During the UX testing process, make sure that you do not influence the opinion of the users in any way. Do not ask them questions that lead them to a particular answer like Do you think this page is too bright? For your questions in a neutral manner.
Also, do not look for feedback on the test. The objective of the test is to get the task done rather than to check what they think is the best color for the dashboard.
i. Welcome the user.
ii. User to sign the non-disclosure.
iii. Provide the incentive.
iv. Start recording device.
v. Purpose, process, and plan.
vi. User not being tested.
vii. OK to express criticism.
viii. Express thoughts verbally.
ix. Explain recordings.
x. Any Questions.
xi. No right & wrong answers.
xii. User doesn’t have to answer
xiii. User is free to leave.
xiv. Follow script.
After the test session:
The tests will do you no good if you do not document it to the T. Once you are done with the tests, compile the results for analysis.
i. Save recordings.
ii. Save notes.
iii. Review information.
Debrief (Researcher should debrief the user):
i. Discuss difficulties.
ii. Probe for more information.
iii. Ask Specific questions.
Reviewing the Test:
Summarize your findings in preset formats. Refer to the test recordings to fill any gaps in your findings. Since you have covered the formats and processes for the documentation beforehand, this step will occur naturally throughout the process of testing.
(Review of notes)-
i. Was the participant successful?
ii. What errors were made?
iii. Summarize the data.
(Memory doesn’t capture sufficient details)-
i. Need notes and recordings.
ii. Recording Trigger memorize.
Reporting:
Based on your test results, work with your designers and/or product managers to analyze the findings. Keep an open mind towards the test as some findings may be completely opposite to your assumptions. That is the point of user testing, don’t get too attached to the design.
(Write the test report and report will include)-
i. Description of the test.
ii. Description of the users.
iii. Findings.
iv. Recommendations for the redesign.
Wrap up!
In today’s world designing for a company, product means that user goals and business goals are aligned. The company or any firm gets profit only when the user is successfully using the product. Building a product not only helps the organization but also successfully meets employee and user’s needs as well.
If you reach so far, osm you did a fab job!
Don’t forget to appreciate this article and clap 50 :)