• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JUnit - testing approaches

 
author
Posts: 799
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Greetings--

Do you discuss testing approaches in the book (e.g. TDD)? What about testing topics such as what is enough testing or how to organize tests? Or are the recipes more geared toward technical solutions (and not philosophy)?

thanks,
Jeff
 
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jeff,

I've been reading the book. It does discuss some of the things about which you ask. Have a look at the table of contents.

Craig
[ August 10, 2004: Message edited by: Craig Demyanovich ]
 
author
Posts: 87
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Do you discuss testing approaches in the book (e.g. TDD)?



Yes. Although I am a TDD practitioner myself, _JUnit Recipes_ is not a TDD book. Some of the recipes are written in the TDD style, but one of my central goals was not to try to sell TDD. I make mention of TDD, refactoring, and the effect of tests on design without preaching about them. There is also plenty of information for people inheriting legacy code who need to test it.

What about testing topics such as what is enough testing or how to organize tests?



The question "what is enough testing" is handled throughout: there are some places where I discuss the ROE (return on effort) for certain kinds of tests, such as for constructors, get/set methods, and so on.

As for how to organize tests, see chapter 3.

Or are the recipes more geared toward technical solutions (and not philosophy)?



You can't get a book from me without a good heaping of philosophy. That said, I tried to present my opinions and my experience without lecturing. The readers can tell me the extent to which I succeeded there.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by J. B. Rainsberger:

You can't get a book from me without a good heaping of philosophy. That said, I tried to present my opinions and my experience without lecturing. The readers can tell me the extent to which I succeeded there.



Well, in my humble opinion, you succeeded quite well.
 
Jeff Langr
author
Posts: 799
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the info gentlemen!

I ordered both JUnit in Action and JUnit Recipes today from Amazon; combined they are a bargain at under $63US.

Best of luck,
Jeff
[ August 11, 2004: Message edited by: Jeff Langr ]
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic