User Acceptance Testing (UAT)

Last published posts

Mobile Application Testing: 10 Steps Approach
Posted on

Mobile application testing is crucial in order to create a reliable product. In this post, we’ll go over the entire testing process step-by-step. Testing is a crucial part of the mobile application lifecycle. However, due to all the time and effort, it takes to complete the full cycle of app testing, it gets overlooked by…
Read more…

Real Agile Approach to Performance Testing
Posted on

Performance testing helps to determine if a system is reliable and comfortable to use. In this post, we’ll explain the main principles of Agile performance testing as well as its benefits. Before launching an app or a website, it’s crucial for a developer and admin to know how the entire system behaves under stressful situations….
Read more…

Posted on

In the development and delivery of software, the most important contribution of DevOps is the elimination of the time lag between project phases: development, testing, trial operation, and delivery of the product to the final consumer. The time2market indicator is one of the key indicators of the competitiveness of products and the success of companies…
Read more…


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


  1. 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
    • o A list of bugs and defects with a description of the problem and a method for its reproduction
  2. Testing methodology (MS Word)
  3. Testing requirements (MS Word or MS Excel or format of specialized tool)
  4. Testing scenarios (MS Word or MS Excel or format of specialized tool)
  5. Test data set (MS Word or MS Excel or format of specialized tool)


  • 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