Object-Oriented Testing Strategies and Planning

Study Notes

Object Oriented Testing Strategies and Tools

Analysis and Design Testing: involves specifying product requirements before testing commences
Unit/Class Tests: test individual units or classes of the software
Integration Tests: test how individual units or classes work together
Validation Tests: verify that the software meets its specified requirements
System Tests: test the entire software system as a whole

Test Planning and Execution

Specify product requirements clearly and quantifiably, considering factors such as portability, maintainability, and usability
Develop a testing plan that emphasizes rapid cycle testing, getting quick feedback from a series of small incremental tests
Conduct formal technical reviews to assess test strategy and test cases

Boundary Value Analysis (BVA)

Involves checking for errors at the boundaries of input values, rather than in the middle
Includes testing maximum, minimum, limits, typical values, and error values
A large number of errors occur at the boundaries of given input values

Equivalent Class Partitioning

Divides the test condition set into partitions that should be treated as the same
Breaks the input domain into groups of data from which test cases should be designed
Allows both true and invalid equivalence groups to be defined
Example: Input conditions are valid between 1 to 10 and 20 to 30

Description

This quiz covers object-oriented testing strategies, including unit tests, integration tests, and system tests. It also discusses test planning and execution for projects, with a focus on specifying product requirements and understanding user needs.