OOtesting - Object Oriented Testing Based on notes from...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Object Oriented Testing Object Oriented Testing Based on notes from James Gain ( [email protected] ) Plus Glenn Blank’s elaborations and expansions
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Objectives Objectives To cover the strategies and tools associated with object oriented testing - Analysis and Design Testing - Class Tests - Integration Tests - Validation Tests - System Tests To discuss test plans and execution for projects analysis design code test
Background image of page 2
Object-Oriented Testing Object-Oriented Testing When should testing begin? Analysis and Design: - Testing begins by evaluating the OOA and OOD models - How do we test OOA models (requirements and use cases)? - How do we test OOD models (class and sequence diagrams)? - Structured walk-throughs, prototypes - Formal reviews of correctness, completeness and consistency Programming: - How does OO make testing different from procedural programming? - Concept of a ‘unit’ broadens due to class encapsulation - Integration focuses on classes and their execution across a ‘thread’ or in the context of a use case scenario - Validation may still use conventional black box methods
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Criteria for Completion of Testing Criteria for Completion of Testing When are we done testing? (Are we there yet?) How to answer this question is still a research question 1. One view: testing is never done… the burden simply shifts from the developer to the customer 2. Or: testing is done when you run out of time or money 3. Or use a statistical model: - Assume that errors decay logarithmically with testing time - Measure the number of errors in a unit period - Fit these measurements to a logarithmic curve - Can then say: “with our experimentally valid statistical model we have done sufficient testing to say that with 95% confidence the probability of 1000 CPU hours of failure free operation is at least 0.995”
Background image of page 4
Strategic Issues Strategic Issues Issues to address for a successful software testing strategy: - Specify product requirements long before testing commences For example: portability, maintainability, usability Do so in a manner that is unambiguous and quantifiable - Understand the users of the software, with use cases - Develop a testing plan that emphasizes “rapid cycle testing” Get quick feedback from a series of small incremental tests - Build robust software that is designed to test itself Use assertions, exception handling and automated testing tools (Junit).
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 19

OOtesting - Object Oriented Testing Based on notes from...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online