Go back to all articles

User Acceptance Testing (UAT)

Mar 20, 2019
3 min read

User Acceptance Testing is a formal test that addresses the needs, demands, and business processes of the user. It is conducted in order to identify the system’s conformance to the acceptance criteria, and to provide the customer or other authorized party with an opportunity to accept or decline the system.

Problems it will solve

  • Minimize the risks related to the incompatibility of the implemented system functionality with the initial business requirements or to the presence of defects in the operation of the new software functionality by promptly discovering these defects during the user acceptance testing
  • Minimizing the duration and costs of the testing

Deliverables

  • 01
    The final report includes the following:
  • Information about how the functionality of the developed software corresponds to the requirements that were specified in the technical documentation
  • Information about the number of defects in the implemented functionality and their severity towards the operation’s capacity of the system
  • A list of bugs and defects with a description of the problem and a method for its reproduction
  • 02
    Testing methodology (MS Word)
  • 03
    Testing requirements (MS Word or MS Excel or format of specialized tool)
  • 04
    Testing scenarios (MS Word or MS Excel or format of specialized tool)
  • 05
    Test data set (MS Word or MS Excel or format of specialized tool)

Scope

  • Analyzing business processes
  • UAT methodology development and coordination with the customer
  • Implementing the test process management system
  • Testing requirements’ development
  • Testing scenarios’ development and preparation of a test data set
  • Testing model coordination with the customer
  • Launching the first iteration of manual testing
  • Launching a follow-up iteration after the defects are corrected by the developer
  • Report

Service Quality Criteria

  • The completion of the project within the timeframe specified by the contract with a test environment availability of no less than 95%.
  • The number of bugs and defects in the system after the release has been installed in the production environment.
  • The number of duplicates or incorrectly entered defects in the test process management system.

Tools and licences

  • HP ALM (HP Application Lifecycle Management, HP Quality center)
  • TFS (Team Foundation Server)
  • TestLink + JIRA
  • TestLink + Readmine
Table of contents

    Related insights in blog articles

    Explore what we’ve learned from these experiences
    8 min read

    Contract Testing : A Complete Guide

    contract testing preview
    Jun 5, 2025

    When you’re working with microservices or APIs, one miscommunication between systems can break your entire application. That’s where you need contract testing. This guide will walk you through what contract testing is, how it works, and why it’s become essential for teams building distributed systems. Whether you’re a developer, QA engineer, or architect, you’ll learn […]

    8 min read

    What Is Spike Testing: Complete Guide

    spike testing preview
    May 30, 2025

    Imagine your application is running smoothly until a flash sale or unexpected traffic surge hits. Suddenly, users can’t log in, pages stop loading, and your team is scrambling to restore service. These unpredictable spikes can overwhelm even the most robust systems if you’re not prepared.  Spike testing is the method used to simulate these sudden […]

    14 min read

    Top 10 Online Load Testing Tools for 2025

    best online load testing tools preview
    May 19, 2025

    In this article, we will go through our favourite features of each of these cloud-based load testing tools, while in the end you will find a parameterized comparison of all of them in one table.

    7 min read

    What Is Chaos Engineering: Overview

    chaos engineering preview
    May 14, 2025

    Chaos engineering is a way to test how complex systems respond to unexpected problems. The idea is simple: introduce controlled failures and watch how the system behaves. This helps uncover weak points before they lead to costly outages. An approach that forces you to think about the unexpected, making it easier to build robust, fault-tolerant […]

  • Be the first one to know

    We’ll send you a monthly e-mail with all the useful insights that we will have found and analyzed