Setup Menus in Admin Panel
Immediate Requirements: QA & Automation Engineer, Lead Performance Engineer, Test Manager & Oracle Consultant. (for candidates in USA) Rush your resumes

Proactive Testing: Risk-Based Test Design Course Content

Overview: Testing is our primary means of reducing risks that systems and software fail to do what they are supposed to and/or do what they are not supposed to do. Test design involves first identifying what tests are needed to give confidence the product/system/software works and then how to carry out those tests. Risks are prioritized to determine which of many potential tests will be performed in limited available time. Traditional testing, which is reactive, tends to miss many potential risks, so that not only does testing not control them but also they in fact are more likely to occur. This course introduces well-known traditional test design methods as well as powerful Proactive Testing: techniques that identify many ordinarily-overlooked risks, while enabling testing the higher risks earlier as well as more. Exercises aid learning.

Pre-Requisites: Focused specifically for beginner to mid-level IT Engineers, QA professionals and Developers.

Proactive Testing: Risk-Based Test Design Course Content Course Content

Chapter 1: Introduction, Course Topics and Value

  • 1.1 Role and need for testing
  • 1.2 Why so many defects occur and fail to be caught
  • 1.3 Developer vs. independent tester
  • 1.4 Opportunities and rewards

Chapter 2: Proactive Test Design Benefits

  • 2.1 Traditional reactive testing limitations
  • 2.2 Proactive Testing: Life Cycle, advantages
  • 2.3 Keys to effective testing.

Chapter 3: Proactive vs. Reactive Test Design

  • 3.1 IEEE Standard for Test Documentation
  • 3.2 Often-overlooked key to proper prioritizing
  • 3.3 Master and detailed test plans
  • 3.4 Test design specifications
  • 3.5 Test case specifications
  • 3.6 Structuring’s added benefits when Proactive

Chapter 4: Identifying Needed Test Designs

  • 4.1 Functional (black box) testing
  • 4.2 Three-level approach to functional testing
  • 4.3 Keys for thoroughness
  • 4.4 Breaking down to manageable pieces
  • 4.5 Functionality Matrix technique
  • 4.6 Use case perspective
  • 4.7 Technical software actions
  • 4.8 Test design specifications that are needed

Chapter 5: Designing Tests More Thoroughly

  • 5.1 How designing adds thoroughness
  • 5.2 Traditional test design still misses a lot
  • 5.3 Focused brainstorming for a better start
  • 5.4 Checklists and guidelines to fill the gaps
  • 5.5 Tests based on data formats
  • 5.6 Coverage of data and process models

Chapter 6: Identifying More Overlooked Test Conditions

  • 6.1 Decision trees and tables
  • 6.2 Concerns common to all types of testing
  • 6.3 Equivalence classes and partitioning
  • 6.4 Ranges and boundary testing
  • 6.5 GUI and navigation issues
  • 6.6 Often-overlooked other dimensions to test

Chapter 7: Making Test Designs Reusable

  • 7.1 Formal/informal test design specifications
  • 7.2 Wordsmithing to make more reusable
  • 7.3 Extracting the reusable elements
  • 7.4 Atomic (simple) reusable test designs
  • 7.5 Business (complex) reusable test designs
  • 7.6 Enhancing with system-specific tests

Chapter 8: Specifying (Reusable) Test Cases

  • 8.1 Translating test designs into test cases
  • 8.2 Selecting scaled subset based on risk
  • 8.3 Reusable test case specifications
  • 8.4 Other essential test case component
  • 8.5 Finding and creating test data
  • 8.6 Test script and matrix formats
  • 8.7 Adding execution consideration refinements
  • 8.8 Link to driving effective automated tests
February 4, 2014
Main Menu