Other Testing Techniques

1
Other Testing Techniques

• CS2335
• Spring 2005

2
Other Testing

• Integration Testing
• GUI Testing
• VV

3
Testing with exceptions

• Generally ignore for CFG/DFG
• Pick normal test cases
• Then analyze exceptions independently
• Throw for each catch block
• All statements executed!
• For correct method see
• http//citeseer.nj.nec.com/395037.html

4
Special Uniques

• Sometimes there are special values we need to
  test that dont strictly meet the criteria of a
  specific technique.
• Y2K 2000 00
• We also need to avoid magic values if possible
  like 2 (5,5)
• Usually these values come from experience

5
Integration Testing

• Big Bang
• Top-Down
• Bottom-Up
• Sandwich
• Feature Set
• Call Graph/Sequence Diagram

6
Top-Down Strategy
Breadth-First Depth-First
Start with Main and Stubs Replace stubs
incrementally Test at each step Regression Test
Suite
DISADVANTAGE A lot of stub writing
7
Bottom-Up Strategy
M5
M4
Start with driver and atomic module Replace
upper drivers with modules Test each
integration Build-up clusters
M3
M2
M1
DISADVANTAGE No program till integration
complete
8
Feature-Set
M1
M4
M5
M2
Board Display
M3
Select Key Features Organize into
clusters Integrate/Test Feature
Load/Save Game
DISADVANTAGE May be hard to isolate features/
Feature Interaction Problem
9
Call Graph / Sequence Diagram

• Pick neighbors, strongly connected classes and
  integrate by pairs.
• Reduces the stub/driver effort

10
Integration Coverage
Code Coverage Static Call Graph Coverage
Number of Use Cases/Scenarios Covered
main
usage
parser
insertsymbol
scanner
getnoblank
getsymbol
11
GUI Testing (Paul Gerrard)

• Test Challenges
• Event-Driven System
• Unsolicited Events
• OO with large number of objects
• Hidden Synchronization
• Hidden Dependencies
• Infinite Input Domain
• Many ways in and out
• Window Management

12
GUI Testing

• Phases
• Low-level (Checklist, Navigation)
• Application(Equivalence, Boundary, State,
  Decision Tables)
• Integration (C/S Communications, Desktop
  integration, Synchronization)
• Non-Functional (Load test, Compatibility)

13
Test Types

• Checklist Standards Conformance
• Navigation Reachability, Call/Event Handling
• Equivalence, Boundary - Input validation,
  Rule-based processing
• C/S Tests attaching to net/dbms
• Synchronization data integrity between windows

14
Coverage Criteria
Problem in Non-Modal Windows

• Event-Flow Graphs
• Cover all events

Help
File
Contents
About
Save
Open
New
Print
Test data shows 92 statement coverage
Page Setup
15
Pulling Testing Together (VV)

• Validation
• Customer review of use cases (Requirements
  validation)
• Traceability (match phases to requirements)
• Validation test suite
• Prototypes
• Alpha/Beta Tests

16
VV Continued

• Verification
• Reviews/Inspections
• Process Monitoring
• Unit Test Standards
• Integration Test Strategy
• Regression Testing
• System Testing

17
Next Time
TQM Lab Extra Credit 1 Point
Bring to class Calculator (Optional but
recommended) Defect Data (Summary form
OK) Category / total number / most common
description For
example 20 / 214 / Missing Package Import
Declaration Blank paper (2
sheets), graph paper usually helpful