Welcome to the next episode in our new series “Integrating testing into your development flow”. Today we are going to be looking at “User Acceptance Testing”.
In our last presentation we will be talking about Integration Testing. Specifically, what it is, when should we do it, who does it, and why is it so important? We went into why most of this type of testing is typically done by a QA manager or test team, not the developer. Including the different types of testing such as big bang, top-down, bottom-up, and sandwich/hybrid approaches. Ending with a real-world use case example of why/how a company would apply it. Plus some tips on the best practices you should consider when doing integration testing.
So today we will be talking about User Acceptance Testing. Specifically, what it is, when should we do it, who does it, and why is it so important?
What Is User Acceptance Testing
User Acceptance Testing (UAT) is testing that an end user or the client performs to verify/accept the software system before moving the software application to the production environment. We typically do UAT in the final phase of testing after functional, integration and system testing. As this is the last step before the product goes live or before the client accepts delivery of the product. In this stage we thoroughly test the product from an end users point of view.
This series comes from our mentoring/mastermind classes. These classes are virtual meetings that focus on how to improve our technical skills and build our businesses. The goals of each member vary. However, this diversity makes for great discussions and a ton of educational value every time we meet. We hope you enjoy viewing this series as much as we enjoy creating it. As always, this may not be all new to you, but we hope it helps you be a better developer.