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 organising or carrying out User Acceptance Testing

Exam Details

There is no exam as part of this course.

Objectives

  • Gain the ability to analyse business requirements to identify test conditions and measure test coverage
  • Be able to document an Acceptance Test plan
  • Understand how to effectively design optimum tests cases and conditions
  • Know how to clearly document defects and how to reproduce problems
  • Be able to monitor and report progress, clearly communicating project status

Choose a location

Please note: this course runs on demand so the price is TBC. It can be arranged to run on-site at your offices as Training for Teams or as a public course if there is sufficient interest.

Please contact us for more details.

Course Content and Agenda

The course content is presented as four modules, spread over two days. There is a large component of practical work in this course, based on a case study that runs through the course.

  1. ​The key objectives of acceptance testing
  2. Verification of business goals
  3. Validation of the software product -  is it suited to its users’ needs?
  4. Typical ways of documenting requirements
  5. Variations within agile, waterfall, and hybrid development environments
  6. Key concepts - prior test levels, what they ought to achieve, the type and level of testing expected in UAT
  1. Test planning
  2. Test requirements definition
  3. Test design
  4. Test construction
  5. Test execution
  6. Practical work, based on a consistent case study
  1. Test design technique for acceptance testing, using decision tables and boundary value analysis
  2. Practical work: continuation of day 1 case study 
  3. “Test-first software development” (or acceptance test-driven design)
  4. Development of test cases (as part of defining business requirements and acceptance criteria, and as examples to guide software design and coding)
  5. Exploration of “testability reviews”
  6. Incident management (“defect tracking”)
  7. Techniques for incident reporting
  1. How to conduct key test management activities
  2. Monitoring and reporting progress towards achieving acceptance criteria
  3. Structuring test progress reports
  4. Handling significant variances from planned progress
  5. Contractual and regulatory issues explained
  6. The importance of clearly documenting acceptance criteria up front
  7. Agreeing defect severity / priority levels
  8. Routes for change requests
Scroll to top