Course Description

User Acceptance Testing

This course is intended for business users, from a non-technical background, who have been given the responsibility for User Acceptance Testing. The course explains the goals of Acceptance Testing and teaches users how to develop tests from requirements, as well as the different levels of documentation involved in today’s software projects. There is a significant practical element to this course, where delegates learn how to create a test plan, design and cross reference tests against requirements and record / report on defects identified during testing.

The User Acceptance Testing course is priced at £595 per delegate excluding VAT. This price includes all course materials, lunch and refreshments. Courses can be arranged at your offices for group bookings of 4 or more delegates. For further details or to request a quote, please Contact Us.

For User Acceptance Testing Services, click here >>

Select the location of your choice, then click a date to book a place:

Course Design

Day 1
UAT in the Testing Lifecycle 
The course begins by introducing the key objectives of Acceptance Testing: to verify that business goals in commissioning the software are achieved, and to validate that the software product is suited to its users’ needs.  Typical ways of documenting these requirements are outlined, with variations found in agile, waterfall, and hybrid development environments. UAT is presented in terms of modern thinking, that “it should not be the customer’s responsibility to debug the system”, but rather to demonstrate its acceptability. The concept of prior test levels, and what they ought to achieve, is used to set expectations as to the type and level of testing that should be conducted in UAT.

The Test Process
This section explains in depth the different activities that should be carried out as a part of the test process; namely Test Planning, Test Requirements Definition, Test Design, Test Construction and Test Execution. There is a significant amount of practical work within this section, based on a consistent case study, including examples for each stage of the process. Delegates are shown how to develop verifiable acceptance criteria and plan tests based on them; to analyse requirements for test conditions; to design tests and test cases; to construct and execute test procedures; to report incidents (defects); and to monitor and report progress. Delegates will come away from this session with the ability to document a test plan, to clearly communicate the scope of testing, before more detailed test preparation activities are carried out.

Day 2
Test Techniques for UAT
Acceptance Testing involves verification that business rules are fully and correctly implemented in the software, and validation that the software runs in ways acceptable to its direct users. This section introduces a key test design technique for Acceptance Testing to ensure systematic 100% coverage of complex business logic, using decision tables and boundary value analysis. In practical work, following the same case study as on Day 1, these techniques will be used in combination to design more detailed test cases, cross referenced back to requirements so as to verify coverage. “Test-first software development” (“Acceptance-Test Driven Design”) will be explained, in which test cases are developed as part of defining business requirements and acceptance criteria, and are provided as examples to guide software design and coding.

Since test-first software development is an emergent approach, not yet adopted by all software development organisations, there is also discussion of “testability reviews”, which are conducted on the basis that specifications from which clear, unambiguous, cost-effective test cases can’t be designed, are specifications from which the correct software can only be built by a combination of good luck and large amounts of expensive rework.

It is not expected that software brought to Acceptance Testing will be perfect. Incident management (“defect tracking”) is explained, including techniques for incident reporting so as to provide developers with the information they need to understand and fix problems encountered in testing.

Test Management and Organisation
The final section of the course explains how to conduct key test management activities when performing Acceptance Testing. This includes monitoring and reporting progress towards achieving Acceptance Criteria (including how to structure test progress reports), with considerations of how to handle significant variances from planned progress. Contractual and regulatory issues are explained, including the importance of clearly documenting acceptance criteria up front with suppliers, and agreeing defect severity / priority levels, and routes for change requests where defects are not accepted as real or important.

Who Should Attend

  • Those with little or no knowledge of testing, but have been given the responsibility for User Acceptance Testing
  • Managers who have the responsibility for carrying out user acceptance testing