15 Implementation Flashcards
(34 cards)
Top-Down Integration
Starting with user-facing shit, and working down. Major faults show up early, but low-level things might not be tested well.
Starting with user-facing shit, and working down.
Top-Down Integration
Bottom-Up Integration
Work from system-facing towards user-facing shit. Everything is tested well, but major design flaws might not appear until the end.
Work from system-facing towards user-facing shit.
Bottom-Up Integration
Doing both bottom-up and top-down integration at once.
Sandwich Integration
Implementation test workflow
Unit testing, product testing, acceptance testing
Testing to Spec, AKA
Black Box Testing
Black Box Testing, AKA
Testing to Spec
Testing to Code, AKA
Glass Box Testing
Glass Box Testing, AKA
Testing to Code
Test-to-Spec
Use specifications to define test cases. Test every possible set of values within specs.
Equivalence Testing
Test in-range, and just outside/inside range.
Testing in-range, and just outside/inside range.
Equivalence Testing
Glass Box test coverage
Statement, Branch, Path
Linear Code Sequences
Points where control flow might jump
Points where control flow might jump
Linear Code Sequences
All-Definition-Use-Path Coverage
Test all paths between variable declaration and use, as IDed by a CASE tool.
Measures of code complexity
LOC or Cyclomatic complexity
Testing when you’re ready to add a new module
Integration Testing
Integration Testing
Testing when you’re ready to add a new module
Testing customer does when they get the product
Acceptance Testing
Testing under load
Stress Testing
Stress Testing
Testing under load
Testing with very large files
Volume Testing
