Do you know why you are doing usability testing?

The first mistake constantly happen is teams don't understand when usability testing can help and when it cannot. Usability testing is a tool to produce information. However, it can't effectively produce all types of information.
These teams often make the mistake of using usability tests to see how the users "feel" about the design. They want to know if the tested participants will favor the design, want to use it again, and share it with their friends.
While these are all important things to find out, a standard usability test is not the way to do it. There are instances where users were extremely frustrated with the design, couldn't complete a single task, yet told they loved it. There are also tests where the users completed every task quickly and effectively, but hated the design, even though they also told they would use it again. It's very hard to know what to change when you get such results.
Because a usability test allows you to observe the user's actual behavior, its real forte is in telling you where the interface causes frustration. The observation of how users flow through the design provides far more actionable information than asking them if they like it or not.
You can avoid this first mistake by being clear what you want to get out of the test. Posing a behavioral questions, like- "Can our users apply for a car loan without confusion?" or "Will the content simplification reduce calls to our support center?". The more detailed the question, the better the results of the test will be. You will know when the design is working and what to do if it is not.