SHI BA29 User Acceptance Testing UAT for Business Analysts BAs Instructions
- June 13, 2024
- SHI
Table of Contents
SHI BA29 User Acceptance Testing UAT for Business Analysts BAs
About this course
All too often the software products delivered to the business do not meet
their expectations, especially with regard to the quality of the product. An
effective User Acceptance Testing (UAT) process addresses this issue by
confirming the functionality and performance of the product prior to its
release. This 2-day workshop looks at the business issues that drive the need
for a fully functional UAT process and describes the components of such a
process. It is designed to help the Business Analyst (BA) develop an
understanding of their role, the process, and the deliverables associated with
UAT.
Audience profile
This course is designed for the Business Analyst professional who is involved
with testing the functionality of technology projects.
At course completion
After completing this course, students will be able to:
- Develop an understanding of basic concepts associated with User Acceptance Testing
- See how UAT applies to the Software Development Lifecycle (SDLC)
- Recognize benefits of improved quality of deployed software using User Acceptance Testing
- Identify the key roles, activities, and deliverables that makeup User Acceptance Testing
- Use a Business Use Case to define scenarios for testing
- Create a UAT test plan and write UAT test cases with associated test data
- Understand the process for testing functional and non-functional requirements
- Identify the challenges of testing vendor-supplied applications
Course Outline
Day 1
-
Background – why is testing important?
- a) Symptoms and sources of quality problems
- b) Benefits of early inspections and reviews
- c) The Quality Maturity Scale
- d) The current state of testing
- e) Challenges in improving quality
-
The Testing Lifecycle – A process overview
- a) What is a testing lifecycle?
- b) Iterative testing principles
- c) Sample testing types
-
Testing Types – A process overview
- a) Classifying testing types
- b) System, Integration, Vendor Validation, Regression, Maintenance, etc.
-
Software Testing – the Basics
- a) What is software testing?
- b) Typical problems that we encounter with software
- c) The Cost of Quality (CoQ) and the cost of finding defects too late
- d) The four stages of software testing (Unit, Integration, System, User Acceptance Testing (UAT)
- e) Testing best practices
- f) Exercise: “How would you test it?” – A new technology is presented to the participants and they are asked to brainstorm what would they test to ensure it is working correctly. (15 minutes)
-
Understanding the Tester’s Terminology
- a) What is UAT and what is the role of the UAT Tester?
- b) Characteristics of a good UAT tester
- c) The tasks of UAT testing
- d) The UAT documents
- e) Common terms & definitions
- i) The three testing techniques
- ii) Testing visibility (White Box, Gray Box, and Black Box testing)
- f) Exercise: UAT Jeopardy – A fun and fast-paced game of Jeopardy – used as a review of terms, concepts, and roles learned in this lesson. (15 minutes)
Day 2
-
The UAT Planning Process
- a) The importance of test planning
- b) What is a Test Plan?
- c) The six steps for creating a Test Plan
- d) General testing tips
- e) Exercise: “Create a Test Plan” – The participants will identify test scenarios from a Business Use Case and identify test objectives and high-level test data for each scenario
-
UAT Test Coverage
- a) What is test coverage?
- b) Using a Requirements Traceability Matrix
- c) Set the testing scope – what to test and what not to test
- d) The Test Coverage Matrix
-
Creating and Executing the UAT Test Cases
- a) What are the goals of testing?
- b) What is a Test Case?
- c) How do Test Plans and Test Cases relate?
- d) The four steps for creating a Test Case
- e) Exercise: “Write a Test Case” – The participants will be asked to write a high-level Test Case from their Business Use Case and define test data for a portion of the steps
- f) Preparing, running, and documenting the Tests
- g) General testing tips and techniques
-
Verifying the Test Results
- a) Documenting test results
- b) What is a defect?
- c) How to log a defect?
- d) The “bug” lifecycle
- e) Writing a good problem description
- f) Taking screen snapshots
- g) 10 tips to avoid writing bad defect reports
- h) Exercise: “Log a defect” – The participants will write a concise and complete statement to explain a defect
- i) Signing-off on the product
-
Testing Vendor-Supplied Applications
- a) Challenges of testing vendor-supplied applications
- b) Challenges to the business
- c) Eight steps for testing vendor-supplied applications
Handout: An industry case study for testing vendor products
User Acceptance Testing (UAT) for Business Analysts (BAs) Course BA29: 2
days Instructor Led
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>