ILT: Acceptance Testing – Simply Put!

Identify, Manage, and Use Business-based Tests for Acceptance Test-Driven Development (ATDD)

Course Duration: 2 Days (14 CDU/PDU)

Select public course date ($1,495/student)
Request dates for your site
Request dates for virtual delivery

Some of this content is also available in our eCourses, eBooks, and KnowledgeKnuggets™

Course Overview

Designing Tests for Acceptance Test-Driven Development (ATDD)

Acceptance Test-Driven Development (ATDD) and Behavior Driven Design BDD) are two of the latest improvements in the Information Technology’s (IT’s) quest to deliver working software quickly, cheaply, and reliably. Test scenarios are business-based situations taken from real life that guide developers in the software creation process. You need to identify and define business tests that will uncover potential errors and increase your confidence in the delivered application’s ability to survive the real world of production.

The key to a successful suite of test cases is to use a wide variety of methods to discover and consolidate testing scenarios that the delivered application must pass to be accepted by the business community. To err is human; to test is to find and eliminate the errors before they proliferate in production.

User acceptance testing without a test plan is similar to taking off without a flight plan. If you do not know what needs to be done to responsibly validate that an information technology solution meets the defined requirements, you place the project (and potentially your organization) at risk.

This business software testing course teaches you how to develop a test plan, organize test scenarios, and manage the testing effort for end-user acceptance testing based on requirements, user stories, and use cases. It also defines and uses test-driven design techniques to identify scenarios to be tested, document the setup criteria, script the execution steps, and establish how to quickly evaluate whether the solution passed or failed the test.

Target Audience

The material in this course will benefit anyone involved in designing or executing end-user acceptance tests, including (but not limited to):

  • Business Analysts
  • Subject Matter Experts
  • Agile Product Owners
  • Project Leaders and Managers
  • Agile team members
  • Systems Analysts
  • Software Testers
  • Solution Architects
  • AND "anyone wearing the business analysis hat"

Learning Objectives

Upon successful completion of this skill-building experience, you can:

  • Defend the need for test-driven development approaches
  • Define the purpose of test scenarios, test scripts, test cases, and test plans
  • Identify components that need to be tested for acceptance of an IT application
  • Determine whether and when to use walkthroughs, reviews, and inspections
  • Create an acceptance test plan that is aligned with your business needs
  • Recognize the 17 key elements of effective test plans
  • Evaluate business events as a source of test scenarios
  • Develop test scenarios based on use case paths and descriptions
  • Extract test scenarios from business and stakeholder requirements
  • Review analysis and design models to identify test scenarios
  • Capture criteria for testing a well-formed user story
  • Create audience-focused test scripts to maximize repeatability
  • Optimize tests using equivalence classes, boundary values, and probable errors
  • Choose the minimal set of test cases to achieve defined testing goals
  • Optimize the use of limited acceptance testing resources
  • Manage your test execution process effectively and efficiently
  • Record, track, and evaluate errors discovered in acceptance testing
  • List the 7 major steps of a well-defined testing methodology
  • Plan to incorporate selected techniques to improve your performance on the job

Course Outline

1 The Truth about Testing

Testing Concepts Defined

  • Conventional Testing Philosophy
  • Test-Driven Concepts
  • Common Test Documentation
  • A Simple Thought Experiment
  • A Tale of Two Testing Objectives

Testing Realities

  • To Test or Not To Test
  • Exercise: Components of IT Solutions
  • What Are You Testing?
  • Discussion: Testable Components
  • Testing Reality

2 The Art and Science of Test Planning

Static Testing Methods

  • Of People and Methods
  • Static Testing Methods
  • Exercise: Static Coverage
  • Rules of Walkthroughs and Inspections
  • Static Validation Methods
  • Implementing Static Testing
  • Exercise: Making It Happen

Dynamic Testing Methods

  • Dynamic Testing Approaches
  • Testing Phases
  • Exercise: Testing Test Phases
  • White Box Testing Defined
  • Black Box Testing Defined

Testing Starts with the Test Plan

  • Test Planning Activities
  • Criteria for a Testing Objective
  • Exercise: Writing Good Test Objectives
  • Defining the Scope of Acceptance Testing

Components of a Test Plan

  • Administrative Components
  • Executive Components
  • Exercise: Phase Transition Guard Conditions
  • Scheduling Components
  • Roles and Responsibilities
  • Planning Required Resources
  • Test Plan Validation

3 Identifying Tests for Test-Driven Development

Defining Test Scenarios

  • Expressing Test Scenarios
  • Default Test Scenario Identification Methodology
  • Exception-Based Test Scenarios
  • Given-When-Then Formatted Tests
  • From Test Scenarios to Test Cases

From Business Events to Test Scenarios

  • Business Events Revisited
  • Extracting Test Scenarios from Business Events
  • Exercise: Business Event Test Scenarios

From Use Cases to Test Scenarios

  • Positive and Negative Testing Use Cases
  • Revealing Test Scenarios using a Use Case
  • Sample Test Scenarios from a Use Case
  • Exercise: Use Case Test Scenarios

From Requirement Statements to Test Scenarios

  • Requirement Types a la BABOK®
  • Requirement Relationships
  • Rules for Effective Requirement Statements
  • Exercise: Requirement-based Test Scenarios

From Diagrams and Models to Test Scenarios

  • Diagrams and Testing
  • Visible Tools
  • Using a Decision Table to Identify Test Scenarios
  • Exercise: Test Scenarios from a Decision Table

From User Stories to Test Scenarios

  • Rules for Effective User Stories
  • Common User Story Structures
  • Exercise: Waist the Waste User Stories
  • User Story-based Test Scenario Identification
  • Exercise: Uncovering Test Scenarios in a User Story

4 From Test Scenarios to Test Cases

Creating Test Scripts

  • Contents of a Test Script
  • Audience-Based Scripting
  • Exercise: Test Script Creation

Engineering Test Criteria

  • Test Engineering
  • Testing Document Structure
  • Test Case Documentation
  • Engineering Test Data
  • Execution Data Engineering
  • Exercise: Applied Test Data Engineering
  • Test Case Completeness Check
  • Test Case Validation

5 Test Execution, Evaluation, and Reporting

Executing Acceptance Testing

  • Test Execution Activities
  • 7 Potential Pitfalls
  • Test Setup Checklist
  • Exercise: Prime Setup Criteria
  • Test Set Grouping Criteria
  • Sequencing Test Sets
  • Exercise: Test Case Grouping
  • Retest Checklist

Reporting Test Results

  • Evaluating the Results
  • Defect Reporting
  • Test Log Content
  • Incident Report Components
  • Problem Resolution Components
  • Defect Isolation versus Debugging
  • Software Error Categories [1]
  • Defect Severity Indicator
  • Test Summary Report

Software Testing Methodology

  • Exercise: Other Testing Terminology
  • A “Real” Testing Methodology
  • Exercise: Testing Activities
  • Test Environment Components (TEC)
  • Capabilities Maturity Model
  • Testing Maturity Model

6 From Showtime to Go Time

Personal Improvement Plan

  • Understanding the Learning Curve
  • Developing Your Personal Implementation Plan


There are no reviews yet.

Be the first to review “ILT: Acceptance Testing – Simply Put!”

Your email address will not be published. Required fields are marked *

You may also like…