User Acceptance Testing for Business Analysts (BA29)
This 2 day workshop looks at the business issues which 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) to develop an understanding of their role, the process, and the deliverables associated with UAT.
Retail Price: $1,195.00
Next Date: 04/29/2024
Course Days: 2
Enroll in Next Date
Request Custom Course
The objectives of this course are to:
- Develop an understanding about 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 which make up 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
Target Participant:
This course is designed for the Business Analyst professional who is involved with testing the functionality of technology projects.
Prerequisites:
It is recommended the participants have a working knowledge of requirements process, requirements elicitation techniques, and computer systems prior to taking this course.
Course Outline
Day 1
- Background – why is testing important?
- Symptoms and sources of quality problems
- Benefits of early inspections and reviews
- The Quality Maturity Scale
- The current state of testing
- Challenges in improving quality
- The Testing Lifecycle – A process overview
- What is a testing lifecycle?
- Iterative testing principles
- Sample testing types
- Testing Types – A process overview
- Classifying testing types
- System, Integration, Vendor Validation, Regression, Maintenance, etc.
- Software Testing - the Basics
- What is software testing?
- Typical problems that we encounter with software
- The Cost of Quality (CoQ) and the cost of finding defects too late
- The four stages of software testing (Unit, Integration, System, User Acceptance Testing (UAT)
- Testing best practices
- 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
- What is UAT and what is the role of the UAT Tester?
- Characteristics of a good UAT tester
- The tasks of UAT testing
- The UAT documents
- Common terms & definitions
- The three testing techniques
- Testing visibility (White Box, Gray Box, and Black Box testing)
- 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
- The importance of test planning
- What is a Test Plan?
- The six steps for creating a Test Plan
- General testing tips
- 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
- What is test coverage?
- Using a Requirements Traceability Matrix
- Set the testing scope – what to test and what not to test
- The Test Coverage Matrix
- Creating and Executing the UAT Test Cases
- What are the goals of testing?
- What is a Test Case?
- How do Test Plans and Test Cases relate?
- The four steps for creating a Test Case
- 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
- Preparing, running, and documenting the Tests
- General testing tips and techniques
- Verifying the Test Results
- Documenting test results
- What is a defect?
- How to log a defect?
- The “bug” lifecycle
- Writing a good problem description
- Taking screen snapshots
- 10 tips to avoid writing bad defect reports
- Exercise: “Log a defect” – The participants will write a concise and complete statement to explain a defect
- Signing-off on the product
- Testing Vendor-Supplied Applications
- Challenges of testing vendor-supplied applications
- Challenges to the business
- Eight steps for testing vendor-supplied applications
- Handout: An industry case study for testing vendor products