• 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 ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Pragmatic Unit Testing in Java 8 with JUnit: what is new

Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Good morning all,

I've read your excellent glorious first book on Pragmatic Unit Testing and I was wondering:
1.) what new things your new book will bring?
2.) have some things become obsolete?

Kind regards,

Posts: 799
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Yvette for the kind words on the book!

As an update to Andy and Dave's 2003 book, I tried to make sure that the examples were a little meatier, since a few of the review complaints were that the code didn't look like the readers' "real world" code. It's based on lots of practical experience with unit testing (something I've been doing for 15+ years).

I think the book brings a new, modern emphasis to unit testing:
- AAA (Arrange/Act/Assert) is heavily emphasized and used
- more cohesive tests, moving in the direction of one assert per test, is heavily emphasized
- designing the tests to act as long-lasting, trustworthy documentation on class capabilities is heavily emphasized
- Hamcrest is used throughout
- Design was emphasized as very important to unit testing (and vice versa), and still is in this version

I don't know that there are any obsolete elements, per se. JUnit has changed a bit, and I hope no one starts with JUnit 3.8-style tests anymore, but I'm sure there's plenty of code out there that still uses the 3.8 framework.

Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic