UAT (Beta Testing)

Mercy Kinoti
Crispytest
Published in
3 min readMay 9, 2019

User Acceptance Testing(UAT) also known as beta testing is the process of conducting a test on whether the product meets the business requirements as well as usability by the end-user.

UAT is critical because it helps identify issues and fix them before launch. This saves time as well as resources. In addition, it ensures users have a quality product.

Objectives of UAT:

  1. To confirm system performance in terms of functionality, usability and compliance to regulations.
  2. To check readibility for production. (launch)
  3. To validate business requirements

Expectations:

Since prior to UAT the product has undergone system testing, it’s expected that its functionality is stable. So basically, UAT focuses on business process validation and it’s not as extensive as system testing.

A No-go recommendation for production implementation. A No go means that there were defects found in the product and it’s not ready to move to production.

UAT Phases

UAT has four phase: test initiation, test design, test execution and closure.

1. Test Initiation:

In this stage, you do the test planning. You identify the dates, environment, participants, communication protocols, roles and responsibilities.

You define the test approach, setup the environment, inform the participants, identify test data requirements.

2. Test Design:

Identification and documentation of business scenarios to be validated. You identify test data and upload the scenario on the appropriate management tool.

3. Test Execution:

This is the deal day. You conduct tests on business scenarios. Collecting defects raised on the test management tools. You can go ahead and re-test the defects raised and perform test regression.

4. UAT Closure:

This is the final stage of testing and the deliverable is a report. In addition to this, a decision on Go or No Go is made.

How to setup for Beta Testing

You have a pool of tools you can use to do your UAT. Some of these tools are:

1. Google

Google play store allows you to have different versions of your app depending on the stage of the development cycle you’re in.

You can upload during alpha testing, beta testing and production. This allows you to have control over the users who have access to your product exclusive to those who you want to participate.

2. Testflight

Upload your beta app on app store connect to start inviting testers on the platform.

3. Amazon device farm

This a testing services for applications ranging from android, iOS and web applications. You receive issues that come up realtime on the various devices.

4. Browser stack

With browser stack, you get to test your websites and mobile apps. You have options like interactive and automated testing.

--

--