New Instruction - Photos from CSC Connect 2009

New Instruction was a featured presenter at CSC Connect 2009

An Overview of the Quality Process

Monday, September 14, 2009 — 8:00 AM - 12:00 Noon
Presented by Peter Briggs, New Instruction, LLC

Introduction: Defect Detection or Defect Prevention?
The objectives of testing are examined and the responsibilities of testers at all levels are defined.
Quality concepts are introduced along with a list of success factors that will facilitate decision-making
at each stage of the testing process. Numerous tests may be conducted during the SDLC and each is
the primary responsibility of a specific group. As each group completes a testing phase a formal
transition process is initiated before the next group begins. This section identifies entrance and exit
criteria by phase for each component of the development team. The object is to eliminate as much
testing overlap as possible.

Objectives / Observations
Impediments to Quality
Roles/Responsibilities of the Tester
Early Testing vs. Late Testing
Quality Improvement Suggestions
Quality Tools and Steps
Opportunities to Improve the Testing Process
System Development Life Cycles - Waterfall SDLC / Spiral SDLC / V-Model
Phase Objectives
Performance / Reliability Metrics
Testing Success Factors
Product Development and Testing Phases

Test Methodologies and Checklists
Testing methodologies enable testers to compute their test coverage and have confidence that all
requirements will be tested. The use of methodologies in testing is an essential element of a quality
assurance organization.

Setting Test Objectives and Identifying Tests
Test Planning
Methodologies
Test Coverage Computation
Boundary Value Analysis
Decision Tables
Exploratory Testing
Checklists – (Table and Array Testing, Date Edits, Screen, Button, and Character Entry Checklists)

Test Planning
Testing begins with a plan that unambiguously states the objectives. A suitable methodology is
selected to provide adequate test coverage and to deliver the desired level of confidence that the
software will perform as advertised. Testing is treated as a dynamic process that may continue after
delivery and will certainly play a role in future system modifications. Appropriate record keeping is
initiated and maintained through the life of the product

Unit Testing (Early Testing)
White Box Test Case Sources
Sample Unit Test Plan Table of Contents
Unit Testing Scenario
Integration Testing and System Testing
System / Acceptance Testing
Sample System (or Acceptance) Test Plan Table of Contents
Sample System (or Acceptance) Test Script
Possible Test Plan Elements
Sample System (or Acceptance) Test Plan
Creating the Regression Test / Regression Test Alternatives
Traceability Matrix
Usability Testing
Test Notebook

Quality ‘Deep Dive’ – More Effective Testing Today

Monday, September 14, 2009 — 1:00 PM - 5:00 PM
Presented by Peter Briggs, New Instruction, LLC

This is a ConnectProject Session. Learn how to move testing and QA techniques from 'gut feelings’ toward an
engineering discipline. We’ll explore risk analysis, testing system upgrades and enhancements, test plan
reviews and defect prevention. An attendee booklet will address the Top 10 Changes to Make Now to Improve
Quality and includes process recommendations that can be applied immediately to improve quality.

Factor Analysis
OATS — Orthogonal Array Testing Strategy
Pairs and Magic Squares

Risk Analysis
In our applications not everything can be tested, so prioritizing the tests is a major requirement of the
tester. For most systems a thorough set of tests may be impractical so identifying those crucial tests
becomes imperative to the tester, we will help to identify those crucial situations.

Categorical Analysis
Factor Breakdown / Operational Matrix

Test Plan Reviews
The test plan is the verification document for the tester; the accuracy of this document could be the
most important phase of the product delivery process. Scrutinizing the application for testability,
completeness, sequencing, structure, and timings are the important factors for determining if the
correct amount of testing has been completed.
Test Modifications
All of our systems will be upgraded or enhanced at some time; the applications must be tested to
ensure that the existing functionality continues to function, but that the new functionality is working
correctly. Analyzing the processes involved making modifications and the testing of those
modifications is crucial to product success.

Maintenance Issues
Maintenance Testing
Estimating the Modifications
Cost Benefit Identification

Defect Prevention
A primary concern for the organization should be ensuring that the mistakes of the past are avoided
in the future. The examination of the past lessons and suggests approaches to resolving problems. It
recognizes that the chief responsibility of testing is defect prevention not defect detection.

Checklists
Functional Specification Defects
Design Defects
Coding Defects
Testing Defects
Coding / Testing Rules

Test Management
Recording results and investigating the origin of defects allows testers to develop measures that will
be used as guidelines for future projects. These documents play a significant role in organizing and
planning the final stages of the development effort.

Test Logs
Sample Defect Tracking Report
Test Log Scenarios
Retesting and Follow-up Procedures
Root Cause Analysis

10 Changes to Make Now to Improve Testing
These are the ten items that New Instruction recommends for the improvement of quality in any
organization. These suggestions when implemented correctly will have greatest possible impact on
your organizational goals.

Requirements Documentation Techniques
Estimates of the Testing Effort
System and Unit Test Plans
Regression Testing
Test Execution Process Management
Incorporating Standards into Our Teams
Formalized Reviews and Walkthroughs
Installing Traceability Into Our Systems
Test Automation
Staff Development & Cross Training