This week's book giveaway is in the Jython/Python forum.
We're giving away four copies of Hands On Software Engineering with Python and have Brian Allbey on-line!
See this thread for details.
Win a copy of Hands On Software Engineering with Python this week in the Jython/Python forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Bear Bibeault
  • Knute Snortum
  • Liutauras Vilda
Sheriffs:
  • Tim Cooke
  • Devaka Cooray
  • Paul Clapham
Saloon Keepers:
  • Tim Moores
  • Frits Walraven
  • Ron McLeod
  • Ganesh Patekar
  • salvin francis
Bartenders:
  • Tim Holloway
  • Carey Brown
  • Stephan van Hulst

Is a 2003 book still useful for learning JUnit ?  RSS feed

 
Ranch Hand
Posts: 182
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I came across what seems to be a nice beginner book to learn JUnit - Pragmatic Unit Testing in Java with JUnit.
Can someone please tell me if this 2003 book would still be relevant today ? If not, is there a similar beginner
book of < 250 pages for learning JUnit ?

Thank you.
 
author & internet detective
Posts: 39054
714
Eclipse IDE Java VI Editor
  • Likes 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
While I love that book, I think you are better off using a book that teaches JUnit 4. "Test Driven" is excellent. It is more than 250 pages. But you dan skip the later chapters as they cover more advanced concepts. And go back to them when you need to test code like that.
 
Ali Gordon
Ranch Hand
Posts: 182
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Jeanne Boyarsky wrote:While I love that book, I think you are better off using a book that teaches JUnit 4. "Test Driven" is excellent. It is more than 250 pages. But you dan skip the later chapters as they cover more advanced concepts. And go back to them when you need to test code like that.



Thanks. I saw test-driven. It has little practical knowledge. I need something more hands on, with the theoretical stuff. I felt like I was in a philosophy
class instead of a developer class when I read that book.
 
Ranch Hand
Posts: 251
Hibernate Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
you can read the below books and both are very good books

1. JUnit Recipes - Practical Methods for Programmer Testing
2. Junit in action
 
Ali Gordon
Ranch Hand
Posts: 182
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Thakur Sachin Singh wrote:you can read the below books and both are very good books

1. JUnit Recipes - Practical Methods for Programmer Testing
2. Junit in action



Have you read those books ? First one us very old and is a recipe book. Second one has poor reviews, but I will check it out.
I hate the "ZZZ in action" series books. Never good for beginners.
 
Jeanne Boyarsky
author & internet detective
Posts: 39054
714
Eclipse IDE Java VI Editor
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Ali Gordon wrote:Thanks. I saw test-driven. It has little practical knowledge. I need something more hands on, with the theoretical stuff. I felt like I was in a philosophy
class instead of a developer class when I read that book.


Can you elaborate on what you found theoretical in "Test Driven"? I found it to be one of the more practical books that I've read. He covers a lot of the scenarios that show up in the real world. Recipe books are the other end of the continuum, but that doesn't sound what you are looking for.

Another way of thinking about this - what are some books you liked the style of? Not about JUnit, just in general. Knowing that will help us recommend something you might like better for JUnit.
 
Marshal
Posts: 67192
169
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Ali Gordon wrote:I hate the "ZZZ in action" series books. Never good for beginners.


It depends upon the book. You need to carefully pay attention to the intended audience for the book. The preface to my jQuery in Action (2nd Ed) book clearly states that the book is not for someone who is completely unfamiliar with JavaScript, though no prior jQuery experience is necessary.
 
Ali Gordon
Ranch Hand
Posts: 182
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Jeanne Boyarsky wrote:

Ali Gordon wrote:Thanks. I saw test-driven. It has little practical knowledge. I need something more hands on, with the theoretical stuff. I felt like I was in a philosophy
class instead of a developer class when I read that book.


Can you elaborate on what you found theoretical in "Test Driven"? I found it to be one of the more practical books that I've read. He covers a lot of the scenarios that show up in the real world. Recipe books are the other end of the continuum, but that doesn't sound what you are looking for.

Another way of thinking about this - what are some books you liked the style of? Not about JUnit, just in general. Knowing that will help us recommend something you might like better for JUnit.



Firstly, I think there is too much blah blah going on. I feel like I am listening in on coder gossip. Sampler -



Why do I need so much fluff ? He can say it like this -

According to different people quality of code can mean - number of defects discovered after using the software, internal or non visible traits like cost of dev, maintenance etc.
Through extensive test coverage (the percentage of your code for which you did tests) and having all the tests automated, TDD effectively guarantees that whatever you have
written a test for works, and the quality (in terms of defects) becomes more of a function of how well we succeed in coming up with the right test cases.
With TDD (test-code-refactor), you save time by writing software in increments that WORK instead of making huge code, testing it in the end and discovering many bugs.


Eg. For theoretical (I found one now) -


Figure 1.6 With incremental development—building the whole system in small increments—we are never
far from an integrated, working code base. This reduces risk, because the inventory of unfinished work
remains small. As we’ll learn later on, incremental development also enables effective learning through
early feedback based on the customer and developers constantly seeing actual, working software



Mark dexter's tuts, although meant to mainly teach eclipse, taught me way more practical TDD with Junit than this book.
 
The only taste of success some people get is to take a bite out of you. Or this tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java
https://coderanch.com/wiki/703735/Programmatically-Create-PDF-Free-Spire
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!