O'Reilly logo

Contributing to Eclipse: Principles, Patterns, and Plug-Ins by Kent Beck, Erich Gamma

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Chapter 17. Finding Tests

Now we get feedback in the form of markers when a test fails. Which tests should we run? There is a strong tendency to be miserly running tests. This seems to be a legacy from the days of limited computing cycles. Our philosophy is to always run all the available tests. When performance makes this totally impossible, we find a way to write more granular tests that provide nearly the same feedback with far fewer CPU cycles. In theory we always run all tests, but we pragmatically allow reality to diverge from this theory on occasion.

Following this theory, we should run all the tests in a project whenever the project changes. How do we find all the tests in a project? In this chapter, we'll learn how to

  • Create type hierarchies ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required