A guide of UAT for Business Analysts

    According to Wikipedia, "User acceptance testing (UAT) consists of a process of verifying that a solution works for the user.". Why is it important? Because lots of things can happen without UAT.

    Here are a few examples of risks when we do not consider UAT:

• Loss of money – this can include losing customers right through to financial penalties for non-compliance to legal requirements;
• Loss of time – this can be caused by transactions taking a long time to process but can include staff not being able to work due to a fault or failure;
• Damage to business reputation – if an organization is unable to provide service to their customers due to software problems then the customers will lose confidence or faith in this organization (and probably take their business elsewhere).

    During the UAT activities, the Business Analyst will create:

• UAT Test Plan
• UAT Test Cases
• After running the tests, the Defect Log captures the problems

    Have you ever worked in BDD environment? Can you imagine the beauty of UAT in BDD? I mention that I captured all the needed cases for User Acceptance in the Gherkin files.

    If you value the UAT and want to learn more, please read this article.