Skip to main content Accessibility help

We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.

Close cookie message
×
Hostname: page-component-84b7d79bbc-c654p Total loading time: 0 Render date: 2024-07-27T23:23:30.028Z Has data issue: false hasContentIssue false

Chapter 12 - Making Sure Your Applications Work—Full Life-Cycle Object-Oriented Testing (FLOOT)

from Part IV - OBJECT-ORIENTED TESTING

Published online by Cambridge University Press:  07 September 2010

Scott W. Ambler
Scott W. Ambler
Affiliation:
AmbySoft Inc., Toronto
Get access

Summary

What We'll Learn in This Chapter

Why we need to test our applications.

Which traditional testing concepts still work for object-oriented (OO) development and which don't.

How to test during all phases of the development life cycle: analysis, design, construction.

How to implement test cases within program code.

How to perform function, regression, stress, and user-acceptance testing.

Testing an object-oriented (OO) application is both very similar and very different as compared to testing a procedural application. The good news, if you can call it that, is that you still need to formulate test cases, you still need to document them, you still need to run and verify them, you still need both black-and-white box tests, you still need regression testing, and you still need stress testing. The bad news, however, is that the new development concepts provided by the OO paradigm require new approaches to testing. In this chapter we will discover several key concepts required for testing object-oriented applications.

I'm a strong believer in something called full life-cycle object-oriented testing (FLOOT), which involves testing your object-oriented applications throughout the entire system development life cycle (SDLC). We'll see that there are many reasons why you want to test throughout the entire SDLC, not the least of which is if you leave testing to the end of a project it typically doesn't get done properly. In this chapter we will discuss a number of testing techniques that together form a FLOOT process (there has to be a music joke in here somewhere).

Type
Chapter
Information
Building Object Applications that Work
Your Step-by-Step Handbook for Developing Robust Systems with Object Technology
 , pp. 363 - 416
Publisher: Cambridge University Press
Print publication year: 1997

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×