Cover of JUnit

JUnit

Pocket Guide

by Kent Beck · first published 2004

2mentions
0recommended by
2HN commenters
2010–2016first – last mentioned

100% neutral

Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Mentions per year

10 2007: 0 mentions2008: 0 mentions2009: 0 mentions2010: 1 mention2011: 0 mentions2012: 0 mentions2013: 0 mentions2014: 0 mentions2015: 0 mentions2016: 1 mention2017: 0 mentions2018: 0 mentions2019: 0 mentions2020: 0 mentions2021: 0 mentions2022: 0 mentions2023: 0 mentions2024: 0 mentions2025: 0 mentions2026: 0 mentions200720172026

What Hacker News says

  • Teeboo · Jun 8, 2016 · Mentions

    …Addison-Wesley. Winner of the Jolt Productivity Award. (ISBN 978-0321146533) 2003. Contributing to Eclipse: Principles, Patterns, and Plugins. With Erich Gamma. Addison-Wesley. (ISBN 978-0321205759) 2004. JUnit Pocket Guide. O'Reilly. (ISBN 978-0596007430) 2004. Extreme Programming Explained: Embrace Change, 2nd Edition. With Cynthia Andres. Addison-Wesley. Completely rewritten. (ISBN 978-0201616415) 2008.…

    on “Mastering Programming: An Outline” ↗
  • Bluem00 · Aug 30, 2010 · Mentions

    …the right thing. Get some kind of testing framework. Look into Test Driven Development as a methodology. With a testing framework, you won't waste time rolling your own. For Java, you could start with JUnit. TDD is a formalized approach to writing test functions as you work, which you already do, while simultaneously designing your code. There are many sources on it around the internet, but Kent Beck's…

    on “Ask HN: How do people really test their code?” ↗

Keyboard shortcuts

/
Focus search
j / k
Next / previous book
Enter
Open focused book
Esc
Close / go back
g h
Go to Home
g t
Go to Top all-time
g m
Go to Most recommended
g r
Go to Rising
g f
Go to For You
?
Show this help